Tool calls
How a tool call looks in the transcript. ChatMessageList chooses the
renderer from its rendering prop, so most apps only set that. The cards are
exported for when you want tool activity somewhere else, such as a feed
beside your own UI.
Rich tool call
The expanded card: tool name, a status badge, arguments and a preview of the result.
Loading the live demo…
RichToolCard props
| Prop | Type | Notes |
|---|---|---|
summary | ToolSummary | Required. The one-line description of the call. |
state | ToolCallState | Required. Status, input and result of the call. |
Minimal tool row
The compact one-line variant, for dense transcripts and side panels.
Loading the live demo…
MinimalToolRow props
| Prop | Type | Notes |
|---|---|---|
summary | ToolSummary | Required. |
state | ToolCallState | Required. |
debug | boolean | Show the raw input and result under the row. |
HTTP tool
A REST call rendered with its method, path, and the response status and body.
Used for distri_request and any tool you map to an HTTP path.
Loading the live demo…
HttpToolCard props
| Prop | Type | Notes |
|---|---|---|
toolCall | ToolCall | Required. input carries method, path and body. |
state | ToolCallState | Status and result, once the call has finished. |
paths | PathConfig[] | Friendly labels for known paths. |
Your own tools
The components above render calls to any tool. To define tools that run in the browser and change your own UI, see In-product tools; the Gallery shows four products built that way.