CCARF Practice Question

Paper 3 · Question 32

D2 Tool Design & MCP Integration · Paper 3

[Scenario 4: Developer Productivity with Claude] You are building developer productivity tooling on the Claude Agent SDK: helping engineers explore unfamiliar codebases, understand legacy systems, generate boilerplate, and automate repetitive tasks — using the built-in tools (Read, Write, Edit, Bash, Grep, Glob) plus MCP servers. The agent attempts an Edit on a legacy file and fails: the anchor text it targeted appears in six places, so the unique-match requirement cannot be satisfied. What is the standard fallback?

• A.Delete five of the six occurrences so the match becomes unique
• B.Retry the same Edit repeatedly until it succeeds
• C.Switch to Bash and modify the file with sed
• D.Use Read to load the full file, then Write the complete modified content — the reliable path when Edit cannot find unique anchor text

Show answer & explanations

Correct answer: D

A: mutilates code to satisfy the tool

B: retries a deterministic failure — the sixfold match will not resolve itself

C: swaps a controlled file operation for fragile stream editing

D: Edit depends on unique text matching; when a file's repetitive structure defeats that, Read + Write performs the modification reliably on the whole file. It is the documented fallback for exactly this failure.

Related Tool Design & MCP Integration questions

More: Paper 3 · All practice questions