concept

Tool use (LLM)

Tool use is the umbrella term for any LLM mechanism that lets the model invoke external functions, APIs, or services — function calling, code interpreter, MCP servers, browser actions.

Tool use turned LLMs into actors instead of just generators. The model emits a structured tool call (function name + arguments), the harness executes it, and the result flows back into the conversation. By 2026 every frontier model supports tool use natively; the engineering question is no longer whether but how to design tools well. Best practices: tight schemas, descriptive names, errors readable by the model, tight result payloads, fewer than ~30 tools per agent.

When to use tool use (llm)

Common mistakes

FAQ

What is tool use (llm)?

Tool use is the umbrella term for any LLM mechanism that lets the model invoke external functions, APIs, or services — function calling, code interpreter, MCP servers, browser actions.

When should I use tool use (llm)?

Any agent. Workflows where the model needs current data or destructive actions.

What are the most common mistakes with tool use (llm)?

Too many tools — mis-routing rates climb past ~30. Vague tool descriptions — the model uses them as documentation. Returning huge JSON dumps — context blows up.

Last updated: 2026-06-01. Raw markdown: https://promtable.com/glossary/tool-use.md.