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.

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

B3.3/5.0
Behavior3/5

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

Annotations already communicate that this is destructive, idempotent, and not read-only. The description adds one useful scoping detail, account ownership of the room, but does not disclose that the action overwrites or replaces an existing slot configuration.

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?

A single, front-loaded sentence with no filler. It communicates the verb, resource, and key scope in eleven words, which is ideal for this dimension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is adequate when combined with the rich schema and annotations, but it omits usage-routing context versus the plural sibling and does not mention constraints like the Pro requirement for slots 5–16, which is only present in the parameter schema.

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%, and the schema already provides detailed meanings for action_number, label, icon, input_type, and others. The description only reinforces the invite_code/action_number relationship via 'numbered quick-action slot' and ownership, adding little beyond the schema.

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 states a specific verb ('configure'), a precise resource ('numbered quick-action slot'), and a scope condition ('room the account owns'). It is clear and distinct from list/trigger siblings, though it does not explicitly differentiate from the very similar sibling update_quick_actions.

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?

The description gives an ownership prerequisite but provides no guidance on when this tool should be used instead of update_quick_actions, trigger_quick_action, or list_quick_actions. An agent is left to infer the appropriate context from sibling names.

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