Tool Calling & Agents · 90 minutes
Trace a tool call from request to answer
Follow one ticket lookup from tool declaration to answer: what the model proposes, what the application validates and executes, and what the assistant says when the result is unavailable.
1.5 h
1
Step 1: The question
Explain the complete lifecycle of get_ticket for TKT-104. Identify the model's role, the application's responsibilities, and what should happen if the result is unavailable.
A ticket status request
User request What is the status of TKT-104?
The application declares one tool for this conversation: get_ticket, which reads a single support ticket and accepts one argument, ticket_id. The model responds with a proposed call.
{"name":"get_ticket","arguments":{"ticket_id":"TKT-104"}}Depending on what the user's organization holds, the handler returns one of these results.
Ticket found
{"ok":true,"ticket":{"id":"TKT-104","status":"open","title":"Settings page crash"}}No accessible ticket
{"ok":false,"code":"not_found"}Constraints
- get_ticket is hosted by the application: application code runs it, not the model
- Only the authenticated session supplies the user's tenant and permissions
Deliverables
- The lifecycle in order, naming who acts at each step
- What the application checks before the handler runs
- What the assistant says for the found ticket and for not_found
2
Step 2: Hints
Optional. Each hint gives a little more away.
3
Step 3: Your answer
Kept in this browser. Saving your score below keeps a copy with it.
0 / 5000
4
Step 4: Reference answer
5
Step 5: Score yourself
Score each dimension 0, 1, or 2, then save the score to your history. Readiness thresholds are editorial estimates.
Grades your written answer against this rubric with your own AI provider key from Settings. It is a second opinion: the score you save is still yours.
0 of 10 · Scored 0 of 5 dimensions
Ready at 8 of 10
Kept in this browser until you sign up, then it moves to your account.
Complete this level when you can explain who proposes, validates, and executes an operation, keep call IDs separate from ticket IDs, and describe how the assistant stops or recovers when a result is unavailable.
Your saved scores
Practice saves and mock interview answers on this question, newest first.
No saved scores yet. Score every dimension, then save.
6
Step 6: Follow-up questions
An interviewer may ask these next.
Does the model execute an application function directly?
What does a tool schema protect?
How is a workflow different from an agent?
Why use a call identifier?
Why must an agent stop?
7