set_human_gate
Arm a human gate on a task to freeze it and record who is waiting, what was asked, and what happens if nobody answers.
Instructions
Arm the human gate on a task: freeze it and record WHO is waiting, WHAT was asked, and WHAT you will do if nobody answers. To end your turn on a question to a person, use ask_human: it posts the question, arms this gate and records your wait in one step; this tool arms a gate without ending your turn. A wait on an agent is ask_agent. Records the whole ask on the task (who is waiting, what was asked, the default), so nothing has to re-read the thread; the '❓ Blocking @' comment marker is still recognised. recommended_default is REQUIRED: a gate with no stated default can only ever be resolved by finding a human. The call takes four answers (credential_exists / reversible / blocked_by_other_task / customer_visible_now), each with one line of justification. The server refuses the arm when the answers show nobody needs to be asked: the credential is held, the action is reversible, and nothing a customer sees or pays changes right now.
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": {
"task_id": "<task_id>",
"reason": "<reason>",
"recommended_default": "<recommended_default>",
"addressee": "<addressee>",
"credential_exists": "<credential_exists>",
"credential_reason": "<credential_reason>",
"reversible": "<reversible>",
"reversible_reason": "<reversible_reason>",
"blocked_by_other_task": "<blocked_by_other_task>",
"blocked_reason": "<blocked_reason>",
"customer_visible_now": "<customer_visible_now>",
"customer_reason": "<customer_reason>"
},
"name": "set_human_gate"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| class | No | 'hard' (default, never auto-released) or 'soft' (released by timeout — the release does NOT answer the question). | |
| reason | Yes | The question itself, in your own words. | |
| task_id | Yes | Task ID to gate. | |
| deadline | No | RFC3339 timestamp when recommended_default applies. Omit for no deadline. | |
| addressee | Yes | @name of the PERSON being asked. Must be a human in the workspace; an agent or unknown name is refused (gate_addressee_not_human). Agents are reached by assign_task, not by a gate. | |
| copy_tier | No | Only when this ask is about VISIBLE PRODUCT COPY (a label, a page's prose, a message users read) — otherwise omit entirely. Answer three questions: (1) is this the company's voice going OUT, or a caption inside the interface? (2) would someone who never opened this screen notice the change? (3) does the text carry a promise — legal, price, product? Any "yes" → tier "A" (external/legal/marketing copy, a promise) and the workspace owner decides. All "no" → tier "B" (a field caption, menu item, system or validation message, section name, an existing dictionary string) and the product lead ships it without asking — the workspace owner sees it after the fact. The server refuses tier "B" outright: ship it yourself, tag the task `copy:b`, quote the exact string in your closing comment. Omitting copy_tier on an ask that reads as copy-approval is refused too, naming this field — state the tier and retry. | |
| reversible | Yes | Is there a rollback anchor — git revert, backup, snapshot, image tag? If you can MANUFACTURE one (take a backup first), the answer is true. | |
| supersedes | No | Only when the previous question on this task already has an answer: say what that answer does not cover. Without it the server refuses a repeat ask (repeat_ask_refused). | |
| canonical_key | No | Optional stable key naming this question. If a human decision is already recorded under the same key, the server refuses the ask (repeat_ask_refused). | |
| blocked_reason | Yes | One line: which card, or why none. | |
| customer_reason | Yes | One line: what the customer would see, or why nothing changes for them now. | |
| credential_exists | Yes | Do you ALREADY hold the credential or access this needs? Check your team's credential store before answering false — a service account your team created for its agents is yours to use. | |
| credential_reason | Yes | One line: which credential, and where you checked. | |
| reversible_reason | Yes | One line: the exact rollback path, or why none exists. | |
| recommended_default | Yes | What you will do if nobody answers. Required — an ask with no default cannot time out. | |
| customer_visible_now | Yes | Does this change what a customer SEES or PAYS right now? A disabled gateway, an inactive flag or a reversible migration is NOT customer-visible; a rate that prints on invoices people already download is. | |
| blocked_by_other_task | Yes | Is the thing you are waiting on actually ANOTHER card? If yes, the answer is add_dependency, not a gate — a blocks edge freezes the feed without adding anything to a human's queue. |