{"version":"2.1.295","anchor":"mcp-tool-normalization-now-dedupes-dropped-tools-and-names","canonical_anchor":"mcp-tool-normalization-now-dedupes-dropped-tools-and-names","heading":"MCP tool lists get an extra cleanup step when schemas are adjusted","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/mcp-tool-normalization-now-dedupes-dropped-tools-and-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### MCP tool lists get an extra cleanup step when schemas are adjusted\n\nWhen Claude Code adjusts an MCP server's tool definitions, its lists of kept and dropped tools now pass through an extra step keyed on tool name\n\n**Unclear.** Whether the extra step removes duplicate tool names is not confirmed.\n\n**What**\n\nMCP (Model Context Protocol) is how Claude Code connects to outside servers that offer extra tools. When a server's tool definitions need adjusting before Claude Code can use them, Claude Code builds two lists: the tools it will offer and the tools it had to drop.\n\nIn two of the places where Claude Code loads MCP tools, both lists now go through an extra step that works on each tool's name before they are used. Claude Code also records when it had to adjust a server's tool definitions in this way.\n\n**Why**\n\nThis may stop the same tool name from showing up more than once when an MCP server's tools are loaded.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}