CCAR-F practice › Tool Design & MCP Integration · Question 31 of 105

Tool Design & MCP Integration

A support agent's lookup_order tool wraps its database call in a catch-all that returns an empty list on any exception. During a database slowdown, the agent tells several customers they have no orders on file. What is the root cause?

Show answer and explanation

Answer: C — The tool reports a failed lookup as a valid empty result, hiding the outage

An empty list means 'the query ran and nothing matched'. Returning it on a timeout turns 'couldn't check' into 'there are none'. The tool should return isError with a transient, retryable category for access failures and keep empty successes for genuine no-match results (c). A prompt rule (a) can't help when the result itself is misleading. A longer timeout (b) treats one symptom and leaves the catch-all in place. Crashing the run (d) removes the agent's chance to retry or explain.