Bluwing
Blog/Product/No tool call is a valid answer4 min left
Start free

On this page

01Why the wrong tool is worse than no tool02How the engine decides03What your app should do with it04The other side: needs_input05The pressure to always answer06Frequently asked questions

Bluwing

HomeBlogWhy it's cheaperFeaturesHow it worksPricing
  1. Blog
  2. Product
  3. 4 min read

No tool call is a valid answer

When nothing fits, the most useful thing an engine can do is decline. Bluwing returns no tool call instead of reaching for the closest one.

Bluwing teamOctober 4, 2026
A grid of quiet tools, with one empty outline where a tool would have been.

On this page

  1. 01Why the wrong tool is worse than no tool
  2. 02How the engine decides
  3. 03What your app should do with it
  4. 04The other side: needs_input
  5. 05The pressure to always answer
  6. 06Frequently asked questions
Back to the top
Key takeaways
  • A closer match is not a match
  • Returning nothing is safer than returning the wrong thing
  • Your app decides what happens when no tool fits

Ask a tool-calling system what's the capital of Peru and watch what happens. If every response must contain a tool call, something has to be chosen. The model picks the least-bad option, your app runs a function that has nothing to do with the question, and the trace looks successful.

Bluwing returns no_tool. It is one of the most useful things the engine does.

#Why the wrong tool is worse than no tool

A missing call is visible. Your app sees that nothing matched and can answer in its own words, ask a clarifying question, or fall back to a plain model. A wrong call is invisible until it has side effects.

Consider a support agent with refund_order, cancel_order and lookup_order. A vague message — this needs sorting out — has no safe default. Choosing cancel_order because the word order appears is not a guess the system should make on the user's behalf.

Rule

if no tool clears the bar, the answer is no tool. There is no "closest match" fallback.

#How the engine decides

The narrowing step produces a ranked branch. A call is only emitted when:

  1. a branch clears the relevance bar;
  2. a leaf inside it clears the tool-level bar;
  3. all required arguments are grounded.

If any of those fails, the turn ends without a call. The response still has the standard shape, so your client does not need a special code path:

json
{
  "finish_reason": "no_tool",
  "tool_calls": []
}

That is the whole contract. Your app can treat it exactly like a model reply with no tool use.

#What your app should do with it

There is no single right answer, but there are three good ones:

  • Answer directly. If your product has a plain chat path, route the turn there.
  • Ask. I can look up orders or start a refund — which one do you need?
  • Do nothing. In a narrow workflow, declining is a correct outcome.

What you should not do is retry with a broader tool list until something matches. That turns a clean decline into the forced guess the engine was avoiding.

#The other side: needs_input

No tool and missing input are different outcomes, and the engine keeps them separate.

StatusMeaningWhat happens next
tool_callsA tool was chosen and its arguments are groundedRun the call
needs_inputA tool was chosen but a required value is missingAsk for the named field
no_toolNothing fitYour app decides

Mixing the last two is a common bug. A missing party size does not mean "no tool fits"; it means the booking tool is right and one field is absent. Keeping them distinct lets your UI respond correctly in both cases.

A ring moving through a grid of quiet tools

#The pressure to always answer

Product teams dislike empty states, and it is easy to add a fallback "just pick something" mode. Resist it. The value of a tool-calling layer is that it knows what it can and cannot do. An engine that always answers is an engine whose answers you cannot trust.

If you need coverage for a question the tools cannot serve, add a tool for it or route it to a model. Do not widen the definition of a match until everything matches.

#Frequently asked questions

Does no_tool cost a credit?

No. You pay one credit per successful resolve. A turn that returns no call is free.

Can I force a tool call?

Not by default. Forcing a call is how invented arguments and wrong tools get through. If your workflow requires an action, make the request more specific or ask the user.

How is this different from a low-confidence answer?

There is no confidence score to tune. The engine either clears the bar or it does not. A threshold you can slide is a threshold that eventually gets slid for the wrong reason.

ProductGuarantees
← PreviousOne credit per turn, and what a turn isNext →What the fast path actually skips
Point your client at Bluwing.Same tool definitions, same tool_calls. One credit per turn, from $4.50 a month.
Start free

Keep reading

GuaranteesOct 204 min

Every argument has to come from somewhere

Language models are good at plausible IDs and dates. Bluwing requires each argument value to appear in the request, the conversation, your facts or an earlier tool result.Read →
ProductSep 183 min

Pin a version, move an alias

Editing tools in production is how a working agent breaks on a Tuesday. Bluwing serves one request from one version, and aliases let you move traffic when you decide.Read →
SecuritySep 104 min

Tool output is data, never instructions

A tool result is text from the outside world. Bluwing treats it as evidence for argument values, never as a command that can change which tool is chosen.Read →
Start freeBluwing logoBluwing

Explore

  • Why it's cheaper
  • Features
  • How it works
  • Pricing
  • Documentation
  • API Reference
  • Comparisons
  • Blog & Guides
  • Privacy Policy
  • Terms of Service
  • System Status

Talk to us

© 2026 Bluwing · bluwing.si. The tool-calling engine for AI agents.

  • Blog→
  • Product Hunt
  • LinkedIn