{
"message_type": "conversation",
"event_type": "conversation.tool_call",
"seq": 310,
"conversation_id": "your-conversation-id",
"inference_id": "550e8400-e29b-41d4-a716-446655440000",
"turn_idx": 5,
"properties": {
"name": "get_weather",
"arguments": "{\"location\":\"NYC\"}",
"tool_call_id": "call_abc123"
}
}Tool Call Event
Outbound: Tavus signals an LLM tool call your client should run.
Configure tools on the PAL: LLM tool calling.
conversation for conversation-layer app messages.
"conversation"
conversation.tool_call.
"conversation.tool_call"
Unix timestamp (seconds since epoch) indicating when this event was created. Use this to build timestamped transcripts or reconstruct the timeline of a conversation.
1746000000.123
Monotonic per event; a higher seq was emitted later. Use with turn_idx as in Event ordering and turn tracking.
42
The unique identifier for the conversation.
"c123456"
This is a unique identifier for a given utterance. In this case, it will be the user utterance that triggered the tool call.
"83294d9f-8306-491b-a284-791f56c8383f"
Turn index; increments when conversation.respond is processed. Groups utterances, tool calls, and speaking-state events for the same turn. See Event ordering and turn tracking.
3
Function name and serialized arguments from the LLM. Tavus does not execute tools server-side-your app performs the call per your integration.
Show child attributes
Show child attributes