{"version":"2.1.248","anchor":"the-mcp-tool-refresh-tool-now-tells-the-model-when-to-use-it","canonical_anchor":"the-mcp-tool-refresh-tool-now-tells-the-model-when-to-use-it","heading":"The MCP tool-refresh tool now tells the model when to use it","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/the-mcp-tool-refresh-tool-now-tells-the-model-when-to-use-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### The MCP tool-refresh tool now tells the model when to use it\n\nClaude now knows when to refresh MCP tool lists, such as after a server reconnects.\n\n**What**\n\nThe tool that re-queries connected MCP servers for their tool lists ships a written description: use it when a device the user says is now open is missing, when an expected tool is absent, or when a server's connection has recovered.\n\n**Details**\n\n- One sentence varies by surface: where MCP tools run inside the REPL the description says refreshed tools become callable there, otherwise that they are available immediately.\n- The choice is made by a runtime function call, not by a settings key.\n\n**Evidence**\n\n`Re-queries the tool list of connected MCP servers and updates the set of available tools, reporting which tools were added or removed.`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}