Skip to main content
Glama

Get Notification

get_notification
Read-onlyIdempotent

Fetch one visible ping by notification id, including its current action_state and, once anything on its data.checklist is checked, checklist_state.

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": "get_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.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, closed-world), and the description adds real behavioral detail: what state fields come back and that checklist_state only appears once a checklist item is checked. It doesn't cover error behavior for unknown or invisible ids, but it goes meaningfully beyond the annotations.

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

Conciseness4/5

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

One front-loaded sentence with no filler. The trailing conditional clause is slightly convoluted in phrasing ('once anything on its data.checklist is checked') but every element carries information.

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?

For a simple single-parameter read with an output schema present, this is close to complete; the description correctly avoids over-explaining return values. Only the absence of routing guidance against siblings leaves a small 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 coverage is 100% and the single parameter is documented as 'Room notification id,' so the schema already carries the load. The description adds only the qualifier 'visible,' which marginally narrows the accepted id space but is not a substantive clarification.

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: 'Fetch one visible ping by notification id.' The 'one ... by id' phrasing implicitly separates it from list_notifications, but no sibling is named, so the differentiation is only partial.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternatives (e.g., wait_for_notification, list_notifications). The word 'visible' hints at a visibility constraint but does not say what happens for a non-visible id or when to prefer this over polling.

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