{"version":"2.1.280","anchor":"new-accountmemory-flag-on-mcp-tool-descriptors-feeding-to","canonical_anchor":"new-accountmemory-flag-on-mcp-tool-descriptors-feeding-to","heading":"New accountMemory flag on MCP tool descriptors, feeding tool-result telemetry","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-accountmemory-flag-on-mcp-tool-descriptors-feeding-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New `accountMemory` flag on MCP tool descriptors, feeding tool-result telemetry\n\nMCP tools can now carry an internal 'accountMemory' flag that feeds into tool-result telemetry\n\n**Unclear.** What accountMemory actually represents or controls beyond being passed into result-tracking is not stated.\n\n**What**\n\nTools provided by MCP servers (Model Context Protocol, a standard for connecting external tools to Claude) can now carry a new internal `accountMemory` flag, defaulting to false and computed by a helper function. When true, it is stored on the tool's info and later used to adjust what gets recorded when that tool's result is tracked.\n\n**Why**\n\nThis is internal plumbing that affects telemetry recording for MCP tool results; it has no direct user-facing behavior described in this change.\n\n- Area: MCP\n- Names: `accountMemory`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}