{"version":"2.1.323","anchor":"system-turn-description-and-file-reference-notes-for-mcp-too","canonical_anchor":"system-turn-description-and-file-reference-notes-for-mcp-too","heading":"Groundwork for MCP tools to describe how they reference files","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/system-turn-description-and-file-reference-notes-for-mcp-too","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Groundwork for MCP tools to describe how they reference files\n\nMCP servers can now carry a note on how their tools refer to files, and tool descriptions can say they describe system turns\n\n**Unclear.** Whether these file-reference notes are sent to the model in this release is not settled.\n\n**What**\n\nMCP (Model Context Protocol) servers connect outside tools to Claude Code. When a server's tools come with a note about how they refer to files, Claude Code can now build a separate block of text for that server holding the note, for the model to read.\n\nTool descriptions can also now be marked as describing system turns, meaning messages that come from Claude Code itself rather than from you.\n\n**Why**\n\nThis lays the groundwork for MCP tools to explain to the model how to handle file references.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}