Session
Check the Tool Call Before You Pay for the Answer
An agent can pick a tool that sounds right but is not, pass a check-out date before the check-in, or turn the city the user named into an airport code. None of these throws an error.
Check tool calls in order of cost: a code check that the expected tool was called, business rules on the parameters inside a hook that blocks the call, and an LLM judge only for the question code cannot answer: do the parameters match what the user meant?
What you'll learn:
• A set of test queries paired with the tool each one should call
• A constraint checker you attach to your agent as a hook
• An intent check that runs only where code cannot decide
• A rule for which check to run on which tool call
• Open source notebooks for every check
Outline:
• The Wrong Tool Call That Does Not Fail
• Check the Tool in Code
• Check the Parameters in Code, With a Hook That Blocks the Call
• Check Intent With an LLM Judge
• Which Check for Which Tool Call
Elizabeth Fuentes Leone
Developer Advocate
San Francisco, California, United States
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top