{"version":"2.1.265","anchor":"declared-tool-tracking-on-transcript-ingest-now-distinguishe","canonical_anchor":"declared-tool-tracking-on-transcript-ingest-now-distinguishe","heading":"Declared-tool tracking on transcript ingest now distinguishes name-only announcements from full entries","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/declared-tool-tracking-on-transcript-ingest-now-distinguishe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Declared-tool tracking on transcript ingest now distinguishes name-only announcements from full entries\n\nTranscript ingest now separately tracks tool declarations that only announce a name versus full tool entries\n\n**What**\n\nWhen Claude Code reads in a transcript and processes declared MCP tools, it now keeps two separate records: `nameOnlyAnnouncements`, for declarations that only give a tool's name, and `entries`, for full tool declarations. Previously, only full entries were merged into the tracked state; name-only announcements weren't handled separately.\n\n**Why**\n\nThis lets Claude Code distinguish a tool that's merely been announced by name from one that's been fully declared, which likely affects how it decides whether a tool is ready to use.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}