Skip to main content
Glama

PingRoom

by io.pingroom
OverviewDiscussionsAdmin

Update Quick Action

update_quick_action
DestructiveIdempotent

Configure a numbered quick-action slot for a room the account owns. Sends a background room refresh to room members' devices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconYesEmoji or icon id.
labelYesButton label. Must be sent, but may be empty ("") — a Ping can be named by its emoji alone, and clients render an untitled one as just the emoji.
soundNoCanonical sound id, e.g. "ting". Omit for the room default.
input_typeNoDetail every press of this action must carry: none (default), location (data.location), link (data.url), file (any attachment), photo (jpg/png attachment) or pdf (pdf attachment). A press without it is a 422 quick_action_input_required.
invite_codeYesRoom invite code.
requires_ackNoWhether pings from this action remain open until one eligible recipient acknowledges them.
action_numberYesQuick-action slot number (1–16). Slots 5–16 require the room owner to have Pro.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesPurpose-built PingRoom result with credential and account fields removed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / input_type
      Added value: +{
+  "description": "Detail every press of this action must carry: none (default), location (data.location), link (data.url), file (any attachment), photo (jpg/png attachment) or pdf (pdf attachment). A press without it is a 422 quick_action_input_required.",
+  "enum": [
+    "none",
+    "location",
+    "link",
+    "file",
+    "photo",
+    "pdf"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • 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
  3. Changed1 schema field changed
    • changedInput schema / properties / label / description
      Previous value: -"Button label."New value: +"Button label. Must be sent, but may be empty (\"\") — a Ping can be named by its emoji alone, and clients render an untitled one as just the emoji."
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the mutation/idempotency profile is covered. The description adds real value beyond that: it discloses a side effect on other users ('sends a background room refresh to room members' devices') and an ownership prerequisite, neither of which is in 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.

Conciseness5/5

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

Two tight sentences, zero waste, with the primary purpose front-loaded ahead of the side-effect note. Nothing needs trimming or reordering.

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?

With a full output schema and rich annotations, the description need not explain returns or safety. It covers purpose, ownership prerequisite, and the cross-device side effect; the only real gap is sibling differentiation against update_quick_actions.

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 all seven parameters (including the enum, sound defaults, and the 1–16 slot range). The description only alludes to 'numbered' slots and adds no syntax or format detail beyond the schema, so the baseline 3 is appropriate.

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 (configure) and resource (numbered quick-action slot) and adds an ownership scope ('a room the account owns'). However, it does not distinguish itself from the near-identical sibling 'update_quick_actions' (plural) or from 'trigger_quick_action', so an agent cannot tell which to pick from the text alone.

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?

No when-to-use guidance and no reference to alternatives. The two nearest siblings (update_quick_actions, trigger_quick_action) are left unmentioned, so nothing tells the agent when this singular tool is preferred over the plural one.

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