Tool call

tool-call is display-only: name, status lifecycle, optional arguments and result. No interaction events.

Live preview

{
  "q": "AgentsKit"
}

"Found"

Demos use docs host CSS. Package primitives are intentionally unstyled so your product theme owns the look.

When to use

• Show what the agent is doing mid-turn
• Surface tool args/result in a consistent panel across shells

Prefer something else when

• Human must approve the tool → approval-request + action confirmation
• Percent progress of a job → progress

Props (schema)

Frame example

{
  "protocol": "agentskit.chat.component",
  "version": 1,
  "type": "render",
  "componentKey": "tool-call",
  "instanceId": "tool-call-fixture",
  "props": {
    "name": "Search",
    "status": "complete",
    "arguments": { "q": "AgentsKit" },
    "result": "Found"
  },
  "fallback": {
    "kind": "tool-call",
    "summary": "Search completed."
  }
}

Events

No events. This key is display-only — do not invent host callbacks.

Host wiring

Display-only — register the component so the frame resolves; no interact handler is required.

import { ToolCallComponent, defineComponentManifest, defineChat } from '@agentskit/chat'

const definition = defineChat({
  id: 'app',
  components: defineComponentManifest([ToolCallComponent]),
  chat: { adapter },
})

For agents

Do not invent props or events outside the schema. Unknown keys and invalid props stay inert.

Shells

Related

• Approval request — Human gate for side effects
• Progress — Percent complete
• Action policy — Tool execution rules
• Live lab — all components side-by-side