Swipe to see each slide.
The short answer
Tool calling, also called function calling, is how an AI model asks for an outside lookup or action, such as an order's status or a calendar booking, instead of only writing text. The model only requests it and your own software carries it out, so allow only approved tools and require sign-off for risky actions.
Three things to remember
- 01The model requests a tool, your software runs it, and the real result goes back to the model.
- 02Tools can look up data, take actions, calculate, connect systems and trigger automations.
- 03Validate every request, limit which tools are available, log requests and results, and require approval for high-impact actions.
Every slide, in words
- 01
What is tool calling?
How AI moves from answering questions to using software
A language model normally generates text.
Tool calling lets it request an outside action or lookup.
Without tools
"What is order 4821's current status?"
The model only knows what is already in context.
With tools
Model requests:
get_order_status(4821)
Software checks the system and returns the real result.
The model does not perform the outside action by itself; your application executes the requested tool.
- 02
How the flow works
User request → tool request → software action → result → answer
User: "Schedule a service visit Friday morning."
Model: Decides a calendar tool is needed.
Tool call: Returns structured arguments for the tool.
Software: Your application runs the calendar action.
Result: The tool returns success, failure, or data.
Model: Uses that result to give the final response.
Tool calling is a coordination pattern between the model and the software around the model.
- 03
What can a tool do?
Any approved function your software exposes to the model
Look up data: Check CRM records, inventory, orders, pricing, schedules, or databases.
Take action: Create a ticket, update a record, schedule a meeting, or start a workflow.
Calculate: Run deterministic math, pricing logic, quoting rules, or other code.
Connect systems: Pass information between approved business applications.
Retrieve content: Fetch documents, policies, product data, or other external context.
Trigger automation: Hand a validated request to an existing automation or integration.
The useful boundary is simple: expose only tools the business actually wants the AI to be able to request.
- 04
Tool calling vs. an AI agent
Tool calling is a capability. An agent uses capabilities in a loop.
Tool calling
One model turn may request one or more tools
Your software executes the approved function
The result returns to the model
Useful even in a simple chatbot or workflow
AI agent
Works toward a goal across multiple steps
May call tools repeatedly
Checks results and decides what to do next
Often includes planning, state, and stop conditions
An agent may use tool calling, but they are not the same thing
Tool calling is one building block of agents, not a synonym for an agent.
- 05
Where the risk lives
The model can request an action, but your system still needs control
Validate every tool argument before executing it
Restrict which tools are available for each user or workflow
Require approval for high-impact actions such as payments, deletes, or external messages
Use normal authentication and permissions in the systems being called
Log tool requests and results so actions can be reviewed
Handle failures and timeouts instead of assuming every tool call succeeded
Model decides what to request. Software decides what is allowed.
Tool calling does not replace permissions, validation, approvals, or application security.
- 06
The small-business takeaway
This is how AI starts working with the software you already use
Tool calling turns AI from a text-only interface into a controlled layer that can interact with real systems.
Answer questions using live business data
Perform approved actions instead of only suggesting them
Connect AI to CRM, scheduling, inventory, quoting, support, and internal tools
Keep deterministic business logic in software while using AI for language and decisions
Add approvals and guardrails anywhere the action carries meaningful risk
The value: AI can help do the work, under your rules.
Start with a narrow tool, a clear business outcome, and permissions that are easy to audit.
More in part 6
- 1What is an AI workflow?
- 2What is an AI agent?
- 3Workflow vs. agent: what's the difference?
- 4Chatbot or AI agent on your website: which do you need?Written
- 5What AI is already built into the software you pay for?Written
- 6How AI works with what you already have
- 7What are automation tools like Zapier, Make and n8n, and where does AI fit?Written
- 8What is RPA, and is it still worth it?Written
- 9What is an integration, really?
- 10What is an API?
- 11What is a webhook?
- 12What is tool calling / function calling?You are here
- 13What is structured output / JSON?
- 14What is MCP?
- 15What is an AI harness?
- 16What are AI skills?
- 17What are subagents?
- 18What is computer use?
- 19What is Jev?
Next step
Where does this fit your business?
Six quick questions about your business, then your AI plan: what to start with, what a person still checks, and the lessons that go with it. Or bring it straight to a free thirty-minute call.
