I notice in the otel traces that call_tool often has ~300-500ms of latency before the the execute / mcp-graphql-client call happens (this is for tools defined in operation files).
Hi @glenn that is much higher than we have seen in our testing, thank you for reporting! Can you give us some more details about how you are running the server and how many tools you have registered? Are you seeing the 300+ms consistently on every request or only on the first tool call?
We have 5 tools via operation files. We consistently see the overhead, not just on the first tool call. The built-in tools seem to be more stable with around 30ms overhead (which is still pretty high I think).
Hi @glenn ,
We’ve been investigating the latency concerns you raised, and I’m happy to share that we recently refactored how we handle operation updates to improve concurrency, which was likely contributing to the overhead you were seeing with operation-based tools.
This fix is now available in the latest release (v1.2.0). Could you give it a try and let us know if you’re still seeing the 300-500ms overhead? We’d love to hear if this resolves the issue for your setup.
Thanks again for taking the time to report this. It really helps us improve the server!