Skip to main content
Glama

Wait for Acknowledgement

wait_for_ack
Read-onlyIdempotent

Long-poll a generic acknowledgement-required ping until its confirmation rule is met (any: first confirmation; all: every original eligible recipient), it expires, or the timeout elapses. Questions use wait_for_answer instead.

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": {
      "notification_id": "<notification_id>"
    },
    "name": "wait_for_ack"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNoSeconds to hold the request open. Use 0 for an immediate authoritative state read.
notification_idYesRoom notification id.

Output Schema

NameRequiredDescriptionDefault
resultYesA privacy-minimized, chainable PingRoom notification result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / result / properties / action_signing_secret
      Added value: +{
      +  "description": "broadcast with a webhook button: the secret every delivery of this ping's buttons is signed with (X-PingRoom-Signature-V2). Returned only here; keep it to verify the deliveries.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / result / properties / actions
      Added value: +{
      +  "description": "The buttons the sender put on the ping: {id, label, type, style}, plus url and host for an open_url button. A webhook button never shows where it goes. Present only on a ping with buttons.",
      +  "items": {
      +    "type": "object"
      +  },
      +  "maxItems": 3,
      +  "type": "array"
      +}
    • addedOutput schema / properties / result / properties / actions_expire_at
      Added value: +{
      +  "description": "When the ping's buttons stop running (24 hours after it was sent).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / result / properties / withdrawn_at
      Added value: +{
      +  "description": "When the sending agent took the ping back with withdraw_notification (null when never). The ping stays in the room's history with its text. Present on reads; on a list or the broadcast answer only once the ping has been withdrawn.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed3 schema fields changed
    • addedOutput schema / properties / result / properties / edited_at
      Added value: +{
      +  "description": "When the sender last replaced the ping's text (null when never). Present on reads; on a list or the broadcast answer only once the ping has been replaced.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / result / properties / replaced
      Added value: +{
      +  "description": "broadcast with a replace_key: true when the send replaced your earlier ping (same id) instead of sending a new one.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / result / properties / tags
      Added value: +{
      +  "description": "Labels the sender put on the ping, sorted alphabetically; [] when none.",
      +  "items": {
      +    "maxLength": 32,
      +    "type": "string"
      +  },
      +  "maxItems": 10,
      +  "type": "array"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / result / properties / checklist_state
      Added value: +{
      +  "description": "Present once an item of data.checklist is checked: ticks[] of {index, checked_at, checked_by.display_name}. A checked item stays checked.",
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / result / properties / origin_agent
      Added value: +{
      +  "description": "Present when a connected agent originated the ping: its handle and display name.",
      +  "type": "object"
      +}
  5. First observed

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds real behavioral detail beyond the annotations: this call blocks, and it returns when the confirmation rule is satisfied, the ping expires, or the timeout elapses, with 'any' vs 'all' semantics spelled out. The safety profile (read-only, idempotent, closed-world) is already carried by annotations, and the description says nothing about concurrency limits or what a still-pending result looks like — though the output schema covers the latter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero padding: the blocking behavior and rule semantics come first, the sibling routing last. Every clause carries information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety and an output schema covering return shape, the description only needs to explain the blocking contract and termination rules, which it does. The minor omission is what the caller should do on a timeout-driven return versus an expiry-driven return.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents both notification_id and timeout, including the timeout=0 immediate-read semantics. The description adds conceptual meaning via the any/all confirmation rule but supplies no parameter-level detail beyond what the schema states, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Long-poll a generic acknowledgement-required ping') plus the exact termination conditions, and explicitly names the sibling it is not (wait_for_answer for questions). An agent can distinguish it from the other wait_* tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit exclusion with the alternative named: questions go to wait_for_answer. Usage context is clear from the termination-condition phrasing, but there is no guidance on when to prefer a non-blocking read (e.g. get_notification) or how the wait relates to approval/handoff waits.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources