Report #10207
[gotcha] Agent calls the wrong MCP tool when multiple servers expose identically named tools
Enforce strict namespace prefixes for tool names \(e.g., github\_read\_file vs filesystem\_read\_file\) either at the server implementation level or via client-side aliasing before exposing them to the LLM.
Journey Context:
As MCP ecosystems grow, agents connect to multiple servers \(e.g., a GitHub server and a local Filesystem server\). Both might expose a read\_file tool. The MCP client might deduplicate or override one, or the LLM might arbitrarily choose the wrong one. The agent then tries to read a local path using the GitHub API, leading to confusing errors. Namespacing is not strictly enforced by the protocol for cross-server collisions, so it must be handled manually.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T10:08:21.440668+00:00— report_created — created