Skip to main content
Glama

PingRoom

by io.pingroom
OverviewDiscussionsAdmin

Update Quick Actions

update_quick_actions
DestructiveIdempotent

Configure several of a room's quick-action slots in one call. Prefer this over repeated update_quick_action: each single-slot write wakes room members' devices with its own background refresh, so setting up four Pings one at a time spends four of a finite daily push budget on one operation. Slots you do not list are left exactly as they are, so this is also the right tool for editing a single Ping.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionsYesAdd new pages as complete groups of four in order (5–8, 9–12, 13–16); the room owner needs Pro. The slots to write. Each action_number must appear at most once. Slots omitted here keep their current configuration — nothing in this tool deletes an action.
invite_codeYesRoom invite code.

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 / actions / items / 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. Changed4 schema fields changed
    • changedInput schema / properties / actions / description
      Previous value: -"The slots to write. Each action_number must appear at most once. Slots omitted here keep their current configuration — nothing in this tool deletes an action."New value: +"Add new pages as complete groups of four in order (5–8, 9–12, 13–16); the room owner needs Pro. The slots to write. Each action_number must appear at most once. Slots omitted here keep their current configuration — nothing in this tool deletes an action."
    • changedInput schema / properties / actions / items / 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 / actions / items / properties / action_number / maximum
      Previous value: -4New value: +16
    • changedInput schema / properties / actions / maxItems
      Previous value: -4New value: +16
  3. Added

TDQS

A4.4/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 safety profile is partly covered. The description adds genuinely useful context beyond them: omitted slots are left exactly as-is (softening the destructive semantics), and each single write triggers a device-waking background refresh against a finite daily push budget. It does not contradict 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?

Front-loaded with the purpose, then the rationale and the single-Ping case. Three sentences, all serving selection; the middle sentence is somewhat long but the push-budget justification is what makes the preference actionable.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. Combined with the routing guidance and the omitted-slot editing semantics, an agent has everything needed to call this correctly.

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 schema itself richly documents action_number, input_type, label, and the omitted-slot behavior. The description adds no parameter-level syntax or field detail beyond what the schema already provides, so baseline 3 applies.

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?

States a specific verb (configure) and resource (a room's quick-action slots) with explicit scope (several in one call). It names the sibling update_quick_action and positions itself against it, so an agent can distinguish the batch tool from the single-slot one without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says to prefer this over repeated update_quick_action and gives the reason (each single-slot write consumes the daily push budget). It also states the non-obvious case where this batch tool is still correct: editing a single Ping. When-to-use is fully specified with the alternative named.

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