A tool call succeeds technically and still creates the wrong business outcome. What do you inspect?
Instruction: Describe how you would debug a tool call that was valid at the API level but wrong for the user.
Context: Tests how the candidate diagnoses the problem, chooses the safest next step, and reasons through recovery. Describe how you would debug a tool call that was valid at the API level but wrong for the user.
Updated
Official answer available
Read the opening below, then unlock the full answer and practical guidance.
I'd compare the requested user outcome, proposed arguments, executed operation, and stored result. A booking tool can return success after reserving the wrong date because it performed the submitted request correctly...
Your preparation path
Work through these questions in order. Read the answer aloud, then explain it in your own words.
1. Start with the foundations
Build the vocabulary and explain the core decisions.
2. Apply it to a real workflow
Practice diagnosis, validation, and everyday tradeoffs.
3. Prepare for senior discussions
Explain failure boundaries, recovery, and production choices.
- Design a fallback strategy when tools are unavailable, degraded, or unauthorized. Member answer
- How do you implement MCP step-up authorization without losing scopes or retrying forever? Member answer
- An MCP request resumes after user confirmation. How would you validate its requestState? Member answer
Related Questions
-
easy
-
easy
-
easy
-
easy
-
easy
-
easy