Skip to main content
Glama
Sign In

PingRoom

by io.pingroom
OverviewDiscussionsAdmin

List Notifications

list_notifications
Read-onlyIdempotent

List a bounded page of recent pings across approved rooms, newest first. Use page to continue while has_more is true.

Input Schema

NameRequiredDescriptionDefault
dateNoOnly pings created on this calendar date, e.g. "2026-08-25".
pageNoPage number, newest first.
typeNoNarrow to pings you received or pings you sent. Omit for both.
limitNoPings per page. Defaults to 10; maximum 25.

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.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds genuinely useful behavioral context beyond them: results are a bounded page, ordered newest first, and iteration is driven by a has_more flag. It omits any note on room-membership prerequisites or rate limits, but that is a minor gap.

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 short sentences, zero filler, with the scope and ordering front-loaded and the pagination instruction following. Every clause earns its place.

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?

An output schema exists, so return values need not be enumerated, and the description still flags the has_more contract the agent must act on. Combined with full schema coverage and safety annotations, little is missing, though a hint about what 'approved rooms' means operationally would close the last gap.

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 schema already documents date, page, type and limit with formats, enum values and bounds. The description mentions 'page' and 'bounded page' but adds no format or default detail beyond the schema, which is the expected baseline when structured fields do the work.

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?

States a specific verb and resource ('List ... pings'), plus scope ('across approved rooms') and ordering ('newest first'), which cleanly separates it from get_notification and wait_for_notification. It stops short of naming a sibling or explicitly contrasting with them, so it is clear but not fully differentiated.

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?

The only guidance is pagination mechanics ('Use page to continue while has_more is true'), which tells the agent how to iterate but not when this tool is the right choice over get_notification, list_rooms, or wait_for_notification. Usage is implied rather than stated, and there are no exclusions.

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