Create Handoff
create_handoffHand work to exactly one human as either an acknowledgement or a tappable question. The server verifies that one of the recipient's current devices supports the complete Handoff action before creating anything.
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": {
"kind": "<kind>",
"prompt": "<prompt>",
"audience": "<audience>"
},
"name": "create_handoff"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Structured context returned on read surfaces after connector privacy filtering. Do not put secrets in data. | |
| kind | Yes | ack asks the human to acknowledge; question asks them to choose an option. | |
| prompt | Yes | The work/request shown to the human. | |
| options | No | Required for question and forbidden for ack. Each item may be a label string or a structured option. | |
| urgency | No | Notification interruption level. Defaults to active. | |
| audience | Yes | ||
| reply_to | No | Optional routing pointer. | |
| expires_in | No | Seconds before the handoff expires; the server clamps this to its safe range. | |
| correlation_id | No | Your own stable correlation id. | |
| idempotency_key | No | Stable key for at-most-once creation across both Ack and Question kinds. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | Purpose-built PingRoom result with credential and account fields removed. |