Function Calling And Tool Use

Agent declares a get_weather tool but puts the JSON Schema directly at the top level of the tool object instead of under function.parameters.

Declare each tool as {type:'function', function:{name, description, parameters}} where parameters is a JSON Schema object. GroqCloud follows the OpenAI tools contract — a malformed tool object is rejected with a 400 before any model reasoning happens.

Assistant turn returns tool_calls with id call_A and call_B. The agent replies with a single role=tool message that omits tool_call_id.

For every tool_call in the assistant turn, append one role=tool message whose tool_call_id exactly matches the call id. Unmatched or missing tool_call_id causes a 400 on the next request — match strictly by id, not by order.

A workflow requires the next assistant turn to call submit_order and nothing else, but the agent leaves tool_choice unset (auto) and sometimes gets a plain-text reply.

Set tool_choice={type:'function', function:{name:'submit_order'}} to force the named call; use 'required' to force some tool; use 'auto' (default) to let the model decide; use 'none' to forbid tool calls. Match tool_choice to the workflow's determinism need.