PingRoom

Trigger Quick Action

trigger_quick_action

Press a room quick action, notifying its members. Rate-limited. Read the action's input_type first (list_quick_actions): location needs data.location, link needs data.url, file/photo/pdf need attachment_ids — a press without the matching detail is a 422 quick_action_input_required.

Input Schema

TableJSON Schema

Name	Required	Description
`data`	No	The detail this press carries. data.location satisfies an action whose input_type is location; data.url satisfies link. Only these two keys are accepted on a trigger.
`ack_mode`	No	Confirmation rule for this press: any (default) resolves on the first confirmation; all waits for every original eligible recipient. Applies only when this press requires acknowledgement.
`is_urgent`	No	Deliver this one press time-sensitive so it breaks through Focus / Do Not Disturb and reaches members who muted the room or you (a block still wins). Send-time only — the action's saved configuration is unchanged.
`invite_code`	Yes	Room invite code.
`requires_ack`	No	Keep this one press open until an eligible recipient acknowledges it. Send-time only and elevating only: true adds the acknowledgement to an action that has none, false never disables the action's stored ack policy.
`action_number`	Yes	Quick-action slot number (1–16). Slots 5–16 require the room owner to have Pro.
`attachment_ids`	No	Ids of up to 4 uploaded attachments (see upload_attachment). Required when the action's input_type is file, photo (jpg/png only) or pdf (pdf only); a mismatched type is a 422 quick_action_input_type.
`trigger_source`	No	Defaults to "manual". Only these two are client-settable — "webhook" and "system" are stamped server-side and are rejected here.
`quick_action_id`	No	Optional id of the action as read from list_quick_actions. When the slot has since moved pages the press is refused with 409 quick_action_layout_changed instead of firing the wrong Ping.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	A privacy-minimized, chainable PingRoom notification result.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 21, 2026

addedInput schema / properties / attachment_ids

Added value: +{
+  "description": "Ids of up to 4 uploaded attachments (see upload_attachment). Required when the action's input_type is file, photo (jpg/png only) or pdf (pdf only); a mismatched type is a 422 quick_action_input_type.",
+  "items": {
+    "format": "uuid",
+    "type": "string"
+  },
+  "maxItems": 4,
+  "type": "array"
+}

addedInput schema / properties / data

Added value: +{
+  "additionalProperties": false,
+  "description": "The detail this press carries. data.location satisfies an action whose input_type is location; data.url satisfies link. Only these two keys are accepted on a trigger.",
+  "properties": {
+    "location": {
+      "additionalProperties": false,
+      "description": "A shareable geographic location.",
+      "properties": {
+        "address": {
+          "description": "Optional formatted street address.",
+          "maxLength": 255,
+          "type": "string"
+        },
+        "label": {
+          "description": "Optional place name shown to the recipient.",
+          "maxLength": 100,
+          "type": "string"
+        },
+        "latitude": {
+          "description": "Latitude in decimal degrees.",
+          "maximum": 90,
+          "minimum": -90,
+          "type": "number"
+        },
+        "longitude": {
+          "description": "Longitude in decimal degrees.",
+          "maximum": 180,
+          "minimum": -180,
+          "type": "number"
+        }
+      },
+      "required": [
+        "latitude",
+        "longitude"
+      ],
+      "type": "object"
+    },
+    "url": {
+      "description": "An absolute http:// or https:// URL.",
+      "format": "uri",
+      "maxLength": 2048,
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / quick_action_id

Added value: +{
+  "description": "Optional id of the action as read from list_quick_actions. When the slot has since moved pages the press is refused with 409 quick_action_layout_changed instead of firing the wrong Ping.",
+  "format": "uuid",
+  "type": "string"
+}

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / is_urgent / description

Previous value: -"Deliver this one press time-sensitive so it breaks through Focus / Do Not Disturb. Send-time only — the action's saved configuration is unchanged."New value: +"Deliver this one press time-sensitive so it breaks through Focus / Do Not Disturb and reaches members who muted the room or you (a block still wins). Send-time only — the action's saved configuration is unchanged."

Changed2 schema fields changedSep 11, 2026

changedInput schema / properties / action_number / description

Previous value: -"Quick-action slot number (1–4)."New value: +"Quick-action slot number (1–16). Slots 5–16 require the room owner to have Pro."

changedInput schema / properties / action_number / maximum
```
Previous value: -4New value: +16
```

Changed1 schema field changedSep 10, 2026

addedInput schema / properties / ack_mode

Added value: +{
+  "description": "Confirmation rule for this press: any (default) resolves on the first confirmation; all waits for every original eligible recipient. Applies only when this press requires acknowledgement.",
+  "enum": [
+    "any",
+    "all"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 1, 2026

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"
+}

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the annotations, it discloses the rate limit, the member-notification side effect, and the 422 quick_action_input_required failure mode. It doesn't contradict annotations.

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 packed sentences front-load purpose, add the rate-limit caveat, and then give the prerequisite; no filler. The dense middle sentence earns its place.

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 complex 9-parameter tool with full schema descriptions, an output schema, and annotations, the description covers the main risk areas: side effect, rate limiting, and input_type-dependent payload requirements. Nothing essential to correct invocation is missing.

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

Parameters4/5

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

Schema covers all 9 parameters, but the description adds cross-parameter meaning: which payload key satisfies which input_type and that file/photo/pdf require attachment_ids. This is valuable beyond individual schema descriptions.

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?

The description uses a clear verb–resource pair–'Press a room quick action'–and states the side effect ('notifying its members'), which separates it from list/update quick-action tools. The title is reinforced without being merely restated.

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?

It tells the agent to read the action's input_type first via list_quick_actions and gives the matching payload mapping before pressing. It stops short of explicit when-not/alternative exclusions, so not a 5.

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

All PingRoom tools Inspect

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

Need Help?