Dev, web & IT
Design, code, host and ship sites and internal tools, with an AI coding agent doing most of the typing.
Tool use lets a model request operations such as retrieving an order or sending a message. Your application executes client-defined functions; providers can execute hosted tools. The surrounding system controls authorization, validation and execution. A structured request is not proof the action is appropriate.
With tool use, you describe the available tools to the model: name, purpose and input fields. The model can reply with a request to call one. OpenAI calls this a multi-step conversation between your application and the model. Anthropic distinguishes client tools, which your application runs, from server tools such as web search, which Anthropic runs for you.
Worked example. A support assistant has a tool lookup_order(order_id). A customer asks, “Where’s order 4471?”
lookup_order with order_id: "4471".For a second tool, refund_order, IonBin recommends an approval step unless the business has explicitly authorized a tightly bounded refund policy enforced by code.
Design, code, host and ship sites and internal tools, with an AI coding agent doing most of the typing.
Hand repeat admin (receipts, logs, notices, handoffs) to workflows your agent can trigger.
Not tool-specific. See Agent-ready for connector support by tool.
Levels come from each tool's recorded, sourced compatibility. How the levels work.
Practitioner views are restated in our words and labeled as views, not measured results. Product facts come from official sources dated above.
IonBin's wiki isn't user-edited. Corrections go to our Directory Curator, who checks them against primary sources before anything changes. Spot something wrong or out of date on “Tool use (function calling)”? Email us with a link to a primary source.
Suggest an edit by email or write to contact@ionbin.com