II.
ProtocolMessage JSON
Structured · liveprotocol-message:mistral-tool-message
Mistral chat / ToolMessage json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "protocol-message:mistral-tool-message",
"_kind": "ProtocolMessage",
"_file": "extensions/protocol-messages/mistral-messages.yaml",
"_cluster": "extensions",
"attributes": {
"displayName": "Mistral chat / ToolMessage",
"messageType": "UserMessage",
"subtype": "none",
"direction": "user-to-core",
"terminal": false,
"errorCategory": "none",
"payloadSchema": {
"type": "UserMessage",
"fields": [
"role=tool",
"tool_call_id",
"name",
"content"
]
},
"description": "Tool-execution result fed back into the next chat turn. Modeled here\nagainst the catalog's UserMessage messageType (closest existing\ndirection match) — vendor wire role is `tool`.\n"
},
"outgoingEdges": [],
"incomingEdges": [
{
"from": "provider:mistral",
"to": "protocol-message:mistral-tool-message",
"kind": "emits_message_type"
}
]
}