Domain roadmap157 words
Domain 2: Tool Design & MCP Integration
Claude Certified Architect - Foundations (CCAR-F) › Domain 2: Tool Design & MCP Integration
Domain 2: Tool Design & MCP Integration
Domain 2 rests on one premise that explains most of its answers: the description is the interface. Tool selection runs on what the descriptions say, so two tools that sound alike get chosen between at close to chance, a constraint left out of a description is a constraint the model cannot respect, and a capable tool that describes itself vaguely loses to a built-in that does not. The second premise is that errors are data: an agent can only recover as well as the error told it what happened.
Domain 2 at a glance
- 18% of scored items
- 5
- 46
- 43, one per published objective
What the guide measures here
- Design effective tool interfaces with clear descriptions and boundaries
- Implement structured error responses for MCP tools
- Distribute tools appropriately across agents and configure tool choice
- Integrate MCP servers into Claude Code and agent workflows
- Select and apply built-in tools (Read, Write, Edit, Bash, Grep, Glob) effectively
The order to learn them in
Working through Domain 2
Tool descriptions
Begin with tool descriptions — what belongs in one, and what overlap does. This is the domain's centre of gravity and the source of its most-repeated fact.