{"version":"2.1.304","anchor":"mcp-tool-names-resolved-through-a-lookup-for-telemetry-or-di","canonical_anchor":"mcp-tool-names-resolved-through-a-lookup-for-telemetry-or-di","heading":"MCP tools can be reported under a more specific name","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/mcp-tool-names-resolved-through-a-lookup-for-telemetry-or-di","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### MCP tools can be reported under a more specific name\n\nTools from MCP servers are now looked up for a more specific name, with the generic `mcp_tool` label used only when none is found\n\n**Unclear.** It is not clear what the more specific name is, or whether it appears anywhere a user sees or only in usage reporting.\n\n**What**\n\nMCP stands for Model Context Protocol, a way of connecting outside services to Claude Code so they can offer extra tools. The names of these tools start with `mcp__`.\n\nWhen Claude Code needs a name for one of these tools, it now first tries to look up a more specific name. It uses the generic label `mcp_tool` only when that lookup finds nothing. Before, every such tool was given the generic label.\n\n**Why**\n\nIn practice, MCP tools may now appear under a more specific name instead of all being grouped as `mcp_tool`.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}