[Azure OpenAI Pipeline + Registered Tool] Tool Output Not Utilized in Model's Response

[serendibeats]

Describe the bug When using Open WebUI with Azure OpenAI Pipeline, and utilizing a registered Tool (such as a MCPO Server), the assistant does not appear to reference or utilize the Tool's output in its final response. Even though the Tool is invoked and returns a result, the model replies as if it has not seen the Tool's output.

Steps to reproduce

Set up Open WebUI to use Azure OpenAI via Azure OpenAI Pipeline. Register an external Tool (MCPO Server) and ensure it is correctly configured and being called when relevant. Interact with the assistant and trigger a Tool call (e.g., ask the assistant to fetch logs via the MCPO Tool). Observe that although the Tool is executed and returns a result, the assistant's reply does not reflect or incorporate this result. Expected behavior The assistant should generate a response that references and utilizes the output from the Tool (e.g., including log data or results received from the MCPO Server as part of its response).

Actual behavior The assistant gives an answer that does not take into account the Tool's output, as if the Tool call and its result were ignored.

This issue seems specific to the combination of Azure OpenAI Pipeline and tools. When using OpenAI's own API, the assistant can properly incorporate Tool results in responses. It appears the model does not get the Tool’s result injected into its prompt when responding. As a consequence, the usefulness of tools with Azure OpenAI integrations is greatly diminished. Suggestion Please verify that when using tools with Azure OpenAI Pipeline, the model receives and references the outputs from the tools when generating its final response.

Thank you!

[guptaavi]

I was having the same issue with Azure OpenAI. The problem seems to be related to the the settings for Streaming Mode and 'Native' tool calling. Once I set both Streaming mode and Tool calling to 'Default' in both the User settings AND in the Admin settings for the Model, then the tool responses started working as expected.