# What is a tool call?

A tool call is a structured request from an AI model to run one of the functions it was given, with arguments that match the function's input schema. The app runs the function, sends the result back to the model, and the model uses it to answer or to decide its next step.

## The round trip

1. **The app describes its tools.** Each tool has a name, a description of what it does and when to use it, and an input schema (JSON Schema) for its arguments.
2. **The model decides.** Given your request and those descriptions, the model either answers directly or returns a tool call: the tool's name and the arguments, for example `get_weather` with `{"location": "San Francisco, CA"}`.
3. **The app runs it.** The model never runs anything itself. The app (or, for some built-in tools, the model provider) executes the call.
4. **The result goes back.** The output is added to the conversation, and the model writes its answer or makes another call.

An [AI agent](https://ai-powered.com/academy/glossary/ai-agent) is this loop repeated: call, read the result, decide the next step.

*Diagram: Where a tool call goes.* The model asks for a tool by name with arguments. The app checks with you, runs the tool (through an MCP server, for example), and sends the result back to the model, which answers or calls again.

## Tool calls and MCP

With [MCP](https://ai-powered.com/academy/glossary/mcp), the tools come from MCP servers. The app asks each server for its tools (`tools/list`), passes them to the model, and when the model picks one, sends it to the right server (`tools/call`). The format is the same for every server, which is why one server works in many apps.

## Approvals

Most apps ask before running a tool, and some let you allow a trusted tool for the rest of a conversation. Read the arguments before you approve, especially for tools that write, send or delete. A tool can mark itself as read-only (the `readOnlyHint` annotation); ChatGPT, for example, treats every tool without that mark as a write action that needs confirmation.

## Sources

Official documentation, checked on 19 November 2026:

- [Tool use with Claude (Claude docs)](https://platform.claude.com/docs/en/agents-and-tools/tool-use/overview)
- [MCP architecture overview (modelcontextprotocol.io)](https://modelcontextprotocol.io/docs/learn/architecture)

## Related terms

- [MCP](https://ai-powered.com/academy/glossary/mcp): MCP (Model Context Protocol) is an open standard for connecting AI applications to outside tools and data. An AI app connects to small programs called MCP servers, asks each one what it offers, and calls those tools when a task needs them.
- [AI agent](https://ai-powered.com/academy/glossary/ai-agent): An AI agent is a system in which a language model decides, step by step, which tools to use and what to do next to finish a task, checking the result of each step before the next. A fixed script decides nothing; an agent directs its own process.
- [MCP server vs API](https://ai-powered.com/academy/glossary/mcp-server-vs-api): An API is an interface that a program calls with code written for that API. An MCP server offers its capabilities through one shared protocol, describing each tool so that any MCP-compatible AI app can discover and call it without custom code. Many MCP servers are a thin layer over an existing API.
