22 tools = 60 second for Response

API Feedback
1

I find that with 22 tools every Response creation takes slightly less than 60 seconds. Sometimes more, because then I need to redo the step because of the timeout, because 60 seconds happens to be my URL Session default timeout. Note: non-streaming mode.

This image shows a workflow trace of an "MCP Agent" with a hierarchical listing of actions, HTTP requests, and their respective execution times displayed as horizontal bars. (Captioned by AI)
This image shows a workflow trace of an "MCP Agent" with a hierarchical listing of actions, HTTP requests, and their respective execution times displayed as horizontal bars. (Captioned by AI)2438×678 59.7 KB

Of course I guess I would see interim responses with the streaming version, but I haven’t implemented that yet…

1 Like
2

Try with strict:false on all, that way an expiring grammar doesn’t have to be built again.

3

sorry to report that this makes no difference:

The image shows a trace view of an "Agent Workflow" in which the "MCP Agent" executes, listing its tools and making several POST and function calls with their respective response times visualized as horizontal bars. (Captioned by AI)
The image shows a trace view of an "Agent Workflow" in which the "MCP Agent" executes, listing its tools and making several POST and function calls with their respective response times visualized as horizontal bars. (Captioned by AI)2428×670 58 KB