Skip to main content
Glama
Sign In

PingRoom

by io.pingroom
OverviewDiscussionsAdmin

Wait for Notification

wait_for_notification
Read-onlyIdempotent

Long-poll for the next ping. Blocks until one arrives or the timeout elapses — the real-time inbound channel for an agent. Excludes everything your connected human sends (and your own sends); you receive other room members' Pings.

Input Schema

NameRequiredDescriptionDefault
afterNoCursor from the previous call; omit to get the current head.
timeoutNoSeconds to hold the request open (server-capped).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / result / properties / notifications / items / 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 / notifications / items / 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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds important behavior beyond those: it blocks until a ping arrives or timeout elapses, and it filters out the connected human's and the agent's own sends. Return details are left to the output schema.

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?

The description is three tight sentences and front-loads the core action, "Long-poll for the next ping." Every sentence adds useful scope or filtering context without waste.

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?

For a two-parameter wait tool with full schema coverage, annotations, and an output schema, the description covers the key behavioral points: blocking long-poll semantics, timeout, real-time inbound channel, and sender exclusions. No critical calling information is missing.

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 the after cursor and timeout parameters are already documented in the schema. The description only indirectly references timeout behavior and does not add syntax or format details beyond what the schema provides.

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

Purpose4/5

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

The description gives a specific verb and resource: "Long-poll for the next ping." The blocking long-poll and real-time inbound channel framing clearly distinguish it from non-blocking notification siblings, though no sibling is explicitly named.

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

Usage Guidelines3/5

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

It implies this is for waiting on inbound pings and states that human and self sends are excluded, but it does not explicitly contrast with get_notification, list_notifications, or other wait_for_* tools. The agent must infer when to use this blocking wait rather than a non-blocking fetch.

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