owner_ask
Ask the workspace owner a question when you cannot decide something yourself. The owner gets ONE message where they actually are (their messenger, else e-mail) and the question is kept as a task on the board. This call does NOT wait: it returns at once, so name a safe default (for example the option that sends nothing) and continue your work on it. The answer comes back later as an owner_answered event that starts the asking agent through its own trigger, and is always written as a comment on the task. Never put the question into a customer's conversation, and never stop to wait for a person at a terminal.
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": "<question>"
},
"name": "owner_ask"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| default | No | 1-based number of the option that applies when no answer comes in time. Pick the safe one. | |
| options | No | Up to 9 answers to pick from. The owner replies with the number. | |
| task_id | No | Attach the question to this existing task instead of creating one. The task's status and assignee are not changed. | |
| agent_id | No | Ask as this agent: it is the one started with the answer. A session passes its own agent's id. | |
| question | Yes | The question, in the owner's language, with what they need to decide in the text itself. | |
| expires_in | No | How long to wait: "30m", "24h" (default), "3d". Between 5 minutes and 14 days. | |
| in_workspace | No | Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected. | |
| context_thread_id | No | The conversation the question is about. Kept on the task as context; the question is never sent there. |