Skip to content

Commit cea9f36

Browse files
committed
docs(tools): discuss tool name conflicts and how to resolve them
1 parent 42273f1 commit cea9f36

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

docs/docs/concepts/tools.mdx

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -213,6 +213,13 @@ When implementing tools:
213213
9. Consider rate limiting for resource-intensive operations
214214
10. Log tool usage for debugging and monitoring
215215

216+
### Tool name conflicts
217+
218+
MCP client applications and MCP server proxies may encounter tool name conflicts when building their own tool lists.
219+
To resolve these conflicts, we recommend maintaining a unique identifier for each connected MCP server, and prefixing that to the tool name with `___` (three underscores) as a separator.
220+
221+
For example, if two web search MCP servers called `a` and `b` both expose a `search_web` tool, client applications or proxies may consider registering these as `a___search_web` and `b___search_web` to disambiguate them.
222+
216223
## Security considerations
217224

218225
When exposing tools:

0 commit comments

Comments
 (0)