{"version":"2.1.248","anchor":"tools-removed-mid-conversation-now-get-an-explicit-disregard","canonical_anchor":"tools-removed-mid-conversation-now-get-an-explicit-disregard","heading":"Tools removed mid-conversation now get an explicit disregard instruction","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/tools-removed-mid-conversation-now-get-an-explicit-disregard","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Tools removed mid-conversation now get an explicit disregard instruction\n\nTools removed mid-conversation now get their own note telling Claude to disregard them.\n\n**What**\n\nThe reminder Claude Code inserts about tools that are no longer usable was split apart. Tools lost because an MCP server disconnected get one wording; tools whose definitions were loaded earlier and then removed for any other reason get their own note telling the model to disregard those descriptions. Re-added tools are split the same way.\n\n**Details**\n\n- Previously all vanished tools shared one MCP-flavoured message, which read as wrong when the cause was not a disconnect.\n\n**Evidence**\n\n`Definitions of the following tools were loaded earlier in this conversation and their source has since been removed.`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}