{"version":"2.1.248","anchor":"mcp-tool-not-found-errors-now-say-why-the-server-is-unavaila","canonical_anchor":"mcp-tool-not-found-errors-now-say-why-the-server-is-unavaila","heading":"MCP tool-not-found errors now say why the server is unavailable","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/mcp-tool-not-found-errors-now-say-why-the-server-is-unavaila","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### MCP tool-not-found errors now say why the server is unavailable\n\nA missing MCP tool now explains the server's state instead of just saying it doesn't exist.\n\n**What**\n\nWhen the model calls a missing tool whose name begins with `mcp__`, the error now appends a sentence explaining the server's state instead of just saying the tool does not exist. Causes covered are reconnecting, needs_auth, policy_blocked, disconnected, disabled, org_blocked, auth_completed, not_offered, denied and not_configured. This is on for everyone, with no flag involved.\n\n**Details**\n\n- Each cause has two wordings, one for when the server is in context and one for when it is not.\n- The `withdrawn` cause appends nothing.\n\n**Evidence**\n\n`has disconnected. Continue without this tool; it becomes callable again only if the server reconnects.`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}