MCP Tool Name Collisions
Two servers can expose a tool with the same name. Without namespacing, the agent runtime may not know which one the model intended.
Use server-aware names
Some runtimes can prefix local MCP tool names with deterministic server identifiers. OpenAI's Agents SDK, for example, has an opt-in include_server_in_tool_names behavior for local MCP servers.
Prevent collisions before model invocation
Fail or warn during tool assembly rather than silently letting one tool overwrite another. Namespaces make traces and approvals clearer too.
Good namespacing is both correctness and security. A model should never accidentally route a sensitive call to the wrong provider because names collided.