record_execution
Record user action on a committee verdict: mark as executed or declined with a reason, updating the execution ledger.
Instructions
Record whether the user executed or declined a committee verdict, with their reason. Appends to the execution ledger; idempotent — replaying the same record is a no-op, so retries are safe.
Call when the user says "I bought it / I didn't buy / I disagree". When
they decline, ask one short question for the reason first — this closes
the adoption-rate loop that decisions reports on.
Args:
decision_id: "/" from the decisions output.
executed: True if the user acted on the verdict, False if declined.
reason: The user's stated reason (especially when declined).
trade_ids: Optional trade record IDs to link explicitly.
Returns: The stored execution record, or {"status": "error", "error": ...}.
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": {
"decision_id": "<decision_id>",
"executed": "<executed>"
},
"name": "record_execution"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | The user's stated reason (especially when declined). | |
| executed | Yes | True if the user acted on the verdict, False if they declined. | |
| trade_ids | No | Optional trade record IDs to link explicitly. | |
| decision_id | Yes | "<date>/<symbol>" from the decisions tool output. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |