{"version":"2.1.292","anchor":"mcp-tools-with-over-long-names-are-dropped-with-a-warning","canonical_anchor":"mcp-tools-with-over-long-names-are-dropped-with-a-warning","heading":"MCP tools with names that are too long are left out, with a warning","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/mcp-tools-with-over-long-names-are-dropped-with-a-warning","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### MCP tools with names that are too long are left out, with a warning\n\nAn MCP tool whose name is longer than the API allows is no longer sent to Claude, and Claude Code logs a warning for that server\n\n**What**\n\nMCP (Model Context Protocol) servers are outside programs that give Claude extra tools. The API that Claude Code talks to puts a limit on how long a tool's name can be. If a server offers a tool whose name is longer than that limit, Claude Code now leaves the tool out and does not send it to Claude. It writes a warning to that server's log saying the tool is not sent to Claude because of its name. It also records internally that the server is running with a problem, giving a name that is too long as the reason.\n\n**Why**\n\nThis prevents API errors caused by long MCP tool names. The cost is that such a tool simply does not appear for Claude. If a tool from one of your servers seems to be missing, check that server's log for this warning.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}