Skip to main content
Glama
Sign In

PingRoom

by io.pingroom
OverviewDiscussionsAdmin

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.

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. 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"
+}
  2. 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"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavioral context: long-poll holds, the any/all confirmation-rule semantics, and the three ways the call can terminate. It stops short of describing the returned state shape, but with an output schema present that is acceptable.

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 tightly written sentences with no waste; the core action and its termination behavior are front-loaded, and the sibling routing is appended where it belongs.

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

Completeness5/5

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

Given a 2-parameter schema at full coverage, an output schema, and annotations covering the safety profile, the description supplies exactly the missing pieces: long-poll semantics, rule interpretation, and alternative-tool routing.

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 description coverage is 100%, so both parameters (including the 'use 0 for an immediate authoritative state read' nuance) are fully documented in the schema. The description only alludes to the timeout as a terminating condition and adds no syntax or format detail, so the baseline 3 is correct.

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 its scope and termination conditions. It explicitly differentiates itself from the sibling wait_for_answer, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative tool directly with the condition that selects it ('Questions use wait_for_answer instead'), which is exactly the when-not guidance missing from most definitions. The three terminating conditions (rule met, expiry, timeout) further scope its use.

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

All PingRoom toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources