CCAR-F objective 2.1 · Domain 2 · 18% of the exam
Tool Interface Design
The description is the model's only account of what a tool does, so vague descriptions produce exactly the symptoms these items describe: guessed parameter formats, tools picked for adjacent work they do not cover, and a tool abandoned after one failure. Two fixes recur as keys. Put a constraint in the schema as a fixed set of permitted values rather than describing it in prose, because a constraint the model sees as part of the shape stops wrong values being produced instead of translating them afterwards. And shape the result: a tool returning ninety fields spends context on all ninety whether the next decision needs them or not.
8 questions · answers and explanations shown as you go · free, no sign-up
The rest of domain 2: Tool Design and MCP Integration
This domain is 18% of a scored form, about 12 of the 65 questions, spread across 5 objectives. Drill the whole domain or pick another objective below.
One objective is a narrow slice. A full-length timed mock is what tells you whether the whole thing holds together.
Sit a timed mock →