MCP Integration in Claude Code
Last reviewed
Correct answer: D. Defers them, fetching a definition when a task actually needs that tool.
Explanation
The principle — Context is the scarce resource, so the client spends it on tools that turn out to be needed rather than on every tool that might be.
Why the key is correct — Tool search keeps MCP context usage low by deferring tool definitions until Claude needs them, and it is enabled by default. A forty-tool server therefore costs a fraction of what its full schemas would.
Why the others are wrong — Nothing loads all forty schemas upfront. No setting has to be switched on first. And you never load a deferred tool by hand, because the search step does that when a task calls for it.
Remember this — Deferred is the default, and it is invisible in use.
Sources — Anthropic's Claude Code MCP reference.
Sources
“Tool search is enabled by default.”
“Tool search keeps MCP context usage low by deferring tool definitions until Claude needs them.”
Practise 10 questions on this topic
Take MCP Integration in Claude Code — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.