AI models with tool calling: 166 that can call your functions

Tool calling
Services found: 166
#AI modelCapabilitiesAPI $/1M (in / out)Context windowPrice / moOutput $/1MOverviewVisit site
161

Hy4 preview

Tencent
Text & chatReasoningAdjustable thinking
$0.84 / $2.521M tokensAPI only2.52View
162

Fugu Max

Sakana
Text & chatReasoningAdjustable thinking
$2 / $6API only6View
163

Solar Mini 4

Upstage
Text & chatReasoningAdjustable thinking
$0.1 / $0.4512K tokensAPI only0.4View
164

Perceptron Mk1.5

Perceptron
Text & chatVisionAudio
$0.15 / $1.536.9K tokensAPI only1.5View
165

Ling 3.0 Flash VL

InclusionAI
Text & chatVisionVideo
$0.02 / $0.059256K tokensAPI only0.059View
166

Ternary Bonsai 2 27B

PrismML
Text & chatVisionReasoning
262.1K tokensAPI onlyView

Browse by need

Tool calling is what turns a chatbot into software. The model returns a structured call - function name plus typed arguments - and your code executes it, feeds back the result and lets the model continue. Every integration worth building rests on it.

All 166 models here support it, from Claude Fable 5.1 at $50 per million output tokens down to budget options at $0.25. What varies is reliability under pressure: how well the model picks the right tool from a long list, and how many calls it can chain before losing the thread. Frontier models are noticeably better at long chains.

Structured, not guessedThe model returns a typed call, so your code never parses prose to decide what to run.
Chains break at scaleReliability drops as the tool catalogue grows; frontier models hold longer chains together.
Pairs with JSON outputTool calling picks the action, structured output guarantees the shape of the final answer.

Models with this capability

How to choose

  • Keep tool descriptions short and unambiguous — most failures are description problems, not model problems.
  • Limit the catalogue per request; twenty tools is manageable, two hundred is not.
  • Handle partial failure explicitly: models recover better when the error message says what to do next.
  • Cache the tool definitions — they are the same on every call and caching cuts that input cost.

Common mistakes

One giant toolSplitting into several narrow tools raises accuracy far more than prompt tuning.
No timeout on chainsWithout an iteration cap an agentic loop can call tools until the budget is gone.

Who this suits

Integration teamsConnecting an assistant to internal APIs, CRMs and databases.
AutomationWorkflows where the model decides the next step rather than following a script.
Support productsLooking up orders, issuing refunds, checking availability inside the conversation.

Frequently asked questions

What is the difference from structured output?

Tool calling decides which function to run and with what arguments. Structured output constrains the shape of the final answer. Most production systems use both.

Do cheap models call tools reliably?

For a handful of well-described tools, yes. Accuracy drops as the catalogue grows and as chains get longer, which is where frontier models pull ahead.

Can the model run the tool itself?

Not by default — your code executes the call. For models that run code in a vendor sandbox, see code execution.

Can the model call several tools at once?

Most current models support parallel calls, which cuts latency on independent lookups.

What happens if the model invents a tool?

A well-formed implementation rejects unknown names and returns an error the model can act on.

Frequently searched

Ratings 0

Avg. score 0

Rate this page

Help us improve