{"version":"2.1.315","anchor":"mcp-toolslist-reuse-and-unchanged-tool-list-updates-skipped","canonical_anchor":"mcp-toolslist-reuse-and-unchanged-tool-list-updates-skipped","heading":"MCP tool lists can be reused and unchanged refreshes are skipped","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/mcp-toolslist-reuse-and-unchanged-tool-list-updates-skipped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### MCP tool lists can be reused and unchanged refreshes are skipped\n\nClaude Code can now reuse an earlier tool list from an MCP server, and skips updating its state when a refreshed list has not changed\n\n**What**\n\nMCP servers are outside tools and services Claude Code connects to. Claude Code asks each server for the list of tools it offers. Two things change:\n\n- Reuse: a request for that list can now reuse an earlier answer, with options to normalize the list and to validate it for the API.\n\n- Unchanged lists: when a connected server's tool list is the same as before, a refresh no longer updates Claude Code's internal state.\n\nBefore, Claude Code always fetched the list fresh and always replaced its tools.\n\n**Why**\n\nIt cuts down on repeated MCP refreshes that change nothing.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}