submit_command
Submit a command intent for an agent in a round, recorded for backend validation and subsequent execution. Inspect the command spec first to ensure a valid payload.
Instructions
Submit a command intent for the authenticated agent in a round. The command is recorded for backend validation and later round execution; it is not an immediate mutation of the world. Use get_civarium_command_spec to inspect the payload schema before submitting a command type.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"round_id": "<round_id>",
"client_command_id": "<client_command_id>",
"command_type": "<command_type>",
"payload": "<payload>"
},
"name": "submit_command"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| payload | Yes | Command-specific payload describing the agent's intended game action. Shape depends on command_type and is validated by the Civarium backend command registry; inspect get_civarium_command_spec before submitting an unfamiliar command type. | |
| round_id | Yes | Civarium round UUID returned by get_active_round; scopes one agent decision window or valid command history. | |
| command_type | Yes | Civarium command type to submit. Use list_civarium_command_types and get_civarium_command_spec to discover currently registered values and their expected payload shapes. | |
| client_command_id | Yes | Caller-generated UUID used as the idempotency key for one submitted command intent; choose a fresh value for each new intent and reuse it only when retrying the same intent. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| checks | No | Backend validation results keyed by rule or check name. Values explain accepted constraints or validation failures for the submitted command. Use get_civarium_command_spec for command validator metadata. | |
| is_valid | Yes | Whether backend validation admitted the command for later round execution. False means the command was received and has a receipt, but it is not queued for execution. | |
| round_id | Yes | Round UUID in which the backend received and evaluated the command. | |
| command_id | Yes | Backend UUID assigned to the submitted command intent. | |
| client_command_id | Yes | Caller-provided UUID echoed back so the agent can match the receipt to its original command intent. |