Request the human's acknowledgement (BLOCKS until they ack)
request_ackSend a notification that blocks until the person acknowledges it, ensuring they have seen and confirmed receipt before you continue.
Instructions
Send a message that needs the human to acknowledge it, and BLOCK until they tap 'Acknowledge', then return. Use this when the human must see and confirm receipt of something before you continue (a heads-up they have to read, a checkpoint reached, 'I'm about to start the long run'). The call does not return until the human acks or it times out. Returns { responded, message_id, topic } plus replied_at when acked (responded:true), or { responded: false, reason: "timeout" } if no one acks in time. On timeout/cancel, call check_reply with the returned message_id (replies are retained ~30 min).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Tags / emoji shortcodes, e.g. ["eyes"]. | |
| title | No | Short title, shown bold above the message. | |
| topic | No | Topic to publish to. Pass it explicitly — each project should use its own topic. When omitted, falls back to the project's `.blipr-topic` file, then the BLIPR_TOPIC env var. | |
| message | Yes | What the human needs to see and acknowledge. | |
| priority | No | 1=min/silent … 5=critical. Defaults to 4 (time-sensitive) since it needs an ack. | |
| timeout_seconds | No | How long to block waiting for the acknowledgement before giving up. Defaults to 120s. Some MCP clients cancel a long tool call early; on timeout or cancel, use check_reply with the returned message_id (replies are retained ~30 min). |