Tool name resolution when multiple mcp server have same tool name

[amitsurana]

Pre-submission Checklist

• I have checked that this question would not be more appropriate as an issue in a specific repository
• I have searched existing discussions and documentation for answers

Question Category

• Protocol Specification
• SDK Usage
• Server Implementation
• General Implementation
• Documentation
• Other

Your Question

I haven't come across this problem, but wanted to understand the behavior.
MCP client in general go through all the mcp server that are connected and list the tools that are available. And if there are tools with the same name from different mcp servers, how does mcp client will resolve this? do we add the namespace/server identifier to the tool name to when passed to LLM so that we can pick correct tool name when there are more than 1 tool with the same name?

[amitsurana]

Looks like there is no official way to handle duplicate tool names.
Found this thread - https://github.com/orgs/modelcontextprotocol/discussions/194#discussion-8057544

[esoloz]

You can enforce strict input/output constraints on existing MCP tools using Tool Customization in a MCP Gateway (MCPX).
It lets you wrap tools with fixed parameters, restricted schemas, or overridden descriptions, ensuring agent actions stay within approved boundaries.
Docs: https://docs.lunar.dev/mcpx/tool_customization