Skip to content

Conversation

@3mdistal
Copy link

Summary

  • Adds a note explaining that MCP tools are registered with names like server-name_tool-name
  • Clarifies why glob patterns (e.g., "my-mcp*") are needed instead of exact server names

Related issues: #5373, #2953

Users setting "my-mcp": false in their tools config expect it to disable all tools from that MCP server, but it doesn't work because the actual tool names are prefixed (e.g., my-mcp_search). This note makes the naming convention explicit.

Comment on lines 355 to 361
#### Glob patterns

The glob pattern uses simple regex globbing patterns.

- `*` matches zero or more of any character
- `?` matches exactly one character
- All other characters match literally
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is what this section already states, so instead maybe we should just reword this a bit to be more clear?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed! I edited it.

Copy link

@eXamadeus eXamadeus Dec 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I literally just beat my head against this. This would have saved me over an hour of tweaking.

@3mdistal 3mdistal force-pushed the clarify-mcp-tool-naming branch from 32d4cd9 to 0700c20 Compare December 28, 2025 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants