Tool Calls → UI
Trust dies when tools are invisible. Trust also dies when you dump raw args with tokens.
A restaurant ticket rail: order, station, done — not the chef's tax ID.
Visual Workflows
Start here — scroll inside each diagram frame to explore, then use + / − to zoom up to 200% if needed.
Overview
Scroll inside the frame to explore · use + / − to zoom up to 200%
Scroll inside the frame to explore · use + / − to zoom up to 200%
This turn
Scroll inside the frame to explore · use + / − to zoom up to 200%
A restaurant ticket rail: order, station, done — not the chef's tax ID.
Key Takeaways
- 1.Show what the agent is calling, with args the user is allowed to see.
- 2.Redact secrets. Show status and duration.
- 3.Click through to the observation, not a wall of JSON.
- 4.Failed tools need a retry and error state.
- 5.Trust dies when tools are invisible.
Real Example
Scenario
A restaurant ticket rail: order, station, done — not the chef's tax ID.
What you would do
In AG-UI & Agent UX, apply Tool Calls → UI to this scenario: A restaurant ticket rail: order, station, done — not the chef's tax ID. Identify the inputs, run the technique, validate the output, and note one thing you would monitor in production.
Cheat Sheet
Quick recap
quick ref- •Show what the agent is calling, with args the user is allowed to see
- •Redact secrets. Show status and duration
- •Click through to the observation, not a wall of JSON
Common Mistakes
- ✕Skipping evaluation for Tool Calls → UI before production
- ✕No logging or tracing around tool calls ui steps
- ✕Ignoring cost and latency implications