{"version":"2.1.323","anchor":"toolsearch-already-loaded-wording-and-mcp-redial-changes","canonical_anchor":"toolsearch-already-loaded-wording-and-mcp-redial-changes","heading":"Tool search reconnects only to the failed MCP servers it needs","tier":"notice","area":"Tool Search","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/toolsearch-already-loaded-wording-and-mcp-redial-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Tool search reconnects only to the failed MCP servers it needs\n\nTool search now reconnects only to failed MCP servers that match the search, with a time limit\n\n**What**\n\nTool search is how Claude finds and loads tools that are held back until needed. MCP servers are outside programs that give Claude extra tools. When a search runs, Claude Code used to always try to reconnect to MCP servers. It now does this only for failed servers that match the search, and the attempt is timed.\n\nOther changes:\n\n- The message telling Claude a tool is already loaded, such as \"Already available in this conversation\", now varies in wording.\n\n- Replacing an MCP tool's description of its inputs now also works for some tools picked out by name.\n\nThe `ToolSearch` tool's own description is unchanged in this release.\n\n**Why**\n\nIn practice, searching for tools no longer tries to reach every MCP server each time.\n\n- Area: Tool Search\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}