MCP tool names
An MCP tool name should be 1 to 128 characters of A-Z, a-z, 0-9, underscore, hyphen and dot, unique within the server; the Anthropic directory and the Claude API also cap names at 64 characters, and dots fail there.
Tool names are where the specification and the clients disagree most visibly. The specification allows dots and 128 characters; the Claude API checks names against ^[a-zA-Z0-9_-]{1,64}$, and one name that fails can stop every tool of the connector from loading.
Clients also prefix names with the server name, so a name that fits on its own can overflow once combined. Keep names short, plain and unique.
The 9 checks
- MCP tool name length: 1 to 128 characters: MCP tool names should be between 1 and 128 characters (inclusive); the SDKs warn above 128, and the Claude API and Anthropic directory accept at most 64.
- Allowed characters in MCP tool names: Tool names should use only A-Z, a-z, 0-9, underscore, hyphen and dot (SEP-986); spaces, slashes, commas and non-ASCII letters break clients that turn names into identifiers.
- Tool names are unique within the server: Tool names SHOULD be unique within an MCP server; with a duplicate, a call can reach either tool, clients keep one and drop the other, and the Claude API refuses a request that carries two tools of the same name.
- Tool names of 64 characters or fewer: The Anthropic connector checklist requires tool names of 64 characters or fewer, and Claude validates every name against ^[a-zA-Z0-9_-]{1,64}$, so a longer name, or one with a dot or space, fails.
- Tool names are unique within the server (ChatGPT): OpenAI’s plugin guidelines state that tool names must be unique within your MCP server, so a duplicate name blocks a ChatGPT app submission even though the MCP specification only says SHOULD.
- Tool names without promotional or comparative words: OpenAI’s guidelines say tool names must avoid misleading, overly promotional or comparative language (for example pick_me, best, official); name the action plainly instead, such as get_order_status.
- Tool names that say what the tool does: OpenAI’s guidelines ask you to avoid internal jargon, unexplained acronyms and opaque identifiers in tool names; use a plain verb and object such as list_invoices.
- Larger catalogs use a naming prefix: Once a server has ten or more tools, prefix their names by service or resource (for example asana_search, asana_projects_search) so a model can tell them from similar tools of other servers.
- No look-alike letters from other scripts: A homoglyph uses a letter from another script that looks identical (Cyrillic а for Latin a) so a tool name or word imitates another; tool names should be plain ASCII and every other word should use one script.
Other topics
- MCP tool annotations
- Directory review rules for MCP tools
- MCP tool descriptions
- MCP tool input and output schemas
- Tool poisoning and hidden text
- Write-surface design for MCP tools
- MCP specification 2026-07-28: tools/list rules
Sources last verified on 2026-11-18. How findings become grades.
Check your tool list: paste your tools/list, nothing is sent anywhere