{"version":"2.1.323","anchor":"mcp-directory-listing-tool-gets-whentouse-and-resource-read","canonical_anchor":"mcp-directory-listing-tool-gets-whentouse-and-resource-read","heading":"MCP listing and resource tools now tell Claude when to use them","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-directory-listing-tool-gets-whentouse-and-resource-read","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### MCP listing and resource tools now tell Claude when to use them\n\nClaude Code's MCP directory-listing, connector-listing and resource-reading tools now carry hints on when Claude should use them\n\n**Unclear.** It is not clear whether the directory-listing tool is available to everyone or held behind a separate check.\n\n**What**\n\nMCP (Model Context Protocol) servers are add-ons that give Claude extra tools and data. Some of Claude Code's tools for them are deferred, meaning Claude finds them through tool search instead of seeing them all the time. Several now carry a hint on when to use them:\n\n- The MCP directory-listing tool, which lists one level per call and works only on servers that support directory listing.\n\n- The claude.ai connector listing tool, which also gets an ID in a registry of tools.\n\n- The `ReadMcpResource` tool, which points to the list tool and, for directories, to the directory-read tool.\n\nSuccessful listings now record their use before the result is returned, and `ReadMcpResource` records its result per server.\n\n**Why**\n\nThe hints help Claude pick the right one of these tools when it searches for them.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}