LEVEL 04 · LESSON 29
Tool calling
A tool call is a proposed operation that the application must validate and execute.
What it is
Tool calling lets a model request a defined operation from another system, such as looking up an order or preparing a calendar event.
Why it matters
It connects language-based assistance to live information and business actions. The application still decides what is actually allowed to run.
A business example
A customer asks where an order is. The model requests an order-status lookup with the order identifier. The application checks access, calls the shipping system, and returns the result for the model to explain.
How it actually works
Developers describe available tools, their inputs, and expected results. The model proposes a tool and arguments. Application code validates the request, enforces permissions, executes it, and sends back the outcome. Distinguish read-only tools from tools that change records or send messages. Confirm success from the actual tool result, and use protections against duplicate execution for consequential actions.
A common misconception
A model saying ‘I have updated the order’ is not evidence that an update occurred. The external system’s result is the evidence.
ONE SENTENCE TO REMEMBER
A tool call is a proposed operation that the application must validate and execute.
CHECK YOUR UNDERSTANDING
After a tool call, an assistant replies, “I have updated the delivery address.” How do you know the update happened?
Show the answer
Answer: C.
A tool call is a proposed operation that the application must validate and execute. The model’s statement is not evidence that an update occurred; the external system’s result is.
Take it into your next meeting
How would your interface distinguish a drafted action from a completed one?
One more concept, understood.
Mark this lesson complete to keep your place.