CCAR-F Tool Design and MCP Integration Practice Question
A team is exposing an internal inventory database to Claude through an MCP server. They want the model to retrieve a specific item by its SKU, and they want the tool contract to be unambiguous so the model rarely mis-calls it. Which tool definition best matches this goal?
⚠ Common exam trap
The trap here is equating flexibility in the input schema with better tool design, when narrow, explicit contracts reduce mis-calls.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A `query_inventory` tool whose input schema has a single required string field named `sku`.
The strongest tool contract for a keyed lookup is the one with the fewest, most specific required inputs. A single required `sku` string tells the model exactly what to provide and nothing more, which minimizes ambiguity and downstream errors. Broader or freer schemas trade precision for flexibility that this scenario does not need.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A `query_inventory` tool that takes no parameters and returns the full inventory table.
Why it's wrong here
A no-parameter tool cannot target a specific SKU, so every call returns the entire table, wasting context and making the model filter the result itself. That shifts work onto the model and increases the chance of an incorrect answer. It also fails the stated requirement to retrieve a specific item by SKU.
- ✗
A `query_inventory` tool with optional `sku`, `name`, `category`, and `warehouse` fields, none required.
Why it's wrong here
Four optional fields with no required field means the model can call the tool with nothing useful, or with the wrong field populated. The ambiguity increases the chance of malformed or unhelpful calls. For a lookup keyed on SKU, this design is strictly worse than a single required field.
- ✗
A `query_inventory` tool that accepts a free-form SQL `where` clause string.
Why it's wrong here
A free-form SQL fragment invites injection, makes validation impossible, and forces the model to know the database schema. It also produces highly variable calls that are hard to test. While flexible, it is the opposite of an unambiguous contract and would increase mis-calls rather than reduce them.
- ✓
A `query_inventory` tool whose input schema has a single required string field named `sku`.
Why this is correct
A single required string field named `sku` gives the model one obvious thing to supply and nothing to guess about. The narrow contract reduces ambiguity, so the model is unlikely to invent extra parameters or omit the required one. This directly serves the goal of a low-mis-call tool for SKU lookup.
About these practice questions
Courseiva writes every CCAR-F question from scratch — 271 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Anthropic exam blueprint
This CCAR-F practice question is part of Courseiva's free Anthropic certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CCAR-F exam.