question_answer
Records a human's answer to a pending or defaulted question in a project, with optional notes, and coordinates wake notifications for the asker or lead.
Instructions
Record the human's answer to a pending or defaulted question in this project, plus optional notes. The answer may be a picked option label or free text, including text outside the offered labels. The answer update comes first; the answer and any wake commit together, and the answer stays readable with question_get. An answered or withdrawn question refuses with QUESTION_STATE_CONFLICT. A queued wake carries the question, answer and notes verbatim. When you are the asker, skip with wake_id: null and wake_skipped; otherwise, queue a wake to the running asker or, if the asker has no running row, to the project's running lead with wake_rerouted_to. Skip that fallback with wake_id: null and wake_skipped if no lead runs or the lead is the answerer. wake_id means queued, not delivered.
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": {
"question_id": "<question_id>",
"answer": "<answer>"
},
"name": "question_answer"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | ||
| answer | Yes | ||
| question_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| wake_id | Yes | ||
| hive_notice | No | ||
| question_id | Yes | ||
| wake_skipped | No | ||
| wake_rerouted_to | No |