Report #68953
[gotcha] Agent calls the wrong server's tool due to identical tool names across multiple MCP servers
Namespace tool names explicitly during server configuration \(e.g., github\_read\_file vs local\_read\_file\) rather than relying on the client's implicit disambiguation.
Journey Context:
When attaching multiple MCP servers, name collisions are common \(e.g., two servers exposing search\). While the MCP client might namespace them internally, the LLM often receives a flattened list or gets confused by the implicit prefixes, calling the wrong tool. Explicit, semantic namespacing at the definition level ensures the LLM's attention mechanism correctly differentiates the tools.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T22:13:23.994599+00:00— report_created — created