PingRoom

Create Public Room

create_public_room

Create a publicly discoverable room with a unique @handle. Counts toward the free-plan five-room cap.

Input Schema

TableJSON Schema

Name	Required	Description
`icon`	Yes	A v3 room-icon catalog id, e.g. "bell". Call list_room_icons to discover the valid ids.
`name`	Yes	Room display name.
`color`	Yes	Hex color, e.g. "#e33122".
`handle`	Yes	Globally unique @handle (vanity URL): lowercase letters, digits, underscores.
`category`	No	Discovery category.
`show_owner`	No	Whether the owner is shown publicly. Defaults to true.
`description`	No	Short room description shown in public discovery.
`location_name`	No	Place name shown in nearby discovery. Send all three location fields or none.
`location_latitude`	No	Latitude in decimal degrees. Send all three location fields or none.
`location_longitude`	No	Longitude in decimal degrees. Send all three location fields or none.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Purpose-built PingRoom result with credential and account fields removed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 21, 2026

addedInput schema / properties / location_latitude

Added value: +{
+  "description": "Latitude in decimal degrees. Send all three location fields or none.",
+  "maximum": 90,
+  "minimum": -90,
+  "type": "number"
+}

addedInput schema / properties / location_longitude

Added value: +{
+  "description": "Longitude in decimal degrees. Send all three location fields or none.",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}

addedInput schema / properties / location_name

Added value: +{
+  "description": "Place name shown in nearby discovery. Send all three location fields or none.",
+  "maxLength": 160,
+  "type": "string"
+}

Changed1 schema field changedSep 1, 2026

changedInput schema / properties / icon / description

Previous value: -"Emoji or icon id."New value: +"A v3 room-icon catalog id, e.g. \"bell\". Call list_room_icons to discover the valid ids."

First observedSep 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=false (mutating) and destructiveHint=false (not destructive). The description adds an important business rule: 'Counts toward the free-plan five-room cap', which is not in annotations or schema. It provides practical side-effect information that helps an agent anticipate consequences.

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?

The description is exceptionally concise: two sentences, with the most critical information (public, unique handle, quota impact) front-loaded. No extraneous words, every element serves a purpose.

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?

Given the complexity (10 parameters, output schema exists, annotations cover safety), the description covers the essential business constraint (quota) and public nature. The output schema likely documents return values, so no further explanation is needed. The only minor gap is not explicitly mentioning the handle uniqueness requirement as a parameter constraint, but the schema's pattern provides that.

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%, so all 10 parameters are described in the schema. The description adds no new parameter-level semantics, but it does reinforce the handle uniqueness context. Baseline 3 is appropriate since the schema carries the parameter burden.

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 clearly states verb ('Create'), resource ('a publicly discoverable room'), and a distinguishing constraint ('unique @handle' and free-plan cap). It differentiates from sibling create_room by emphasis on public discoverability and handle uniqueness.

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?

The description implies when to use this tool (creating a public room, as opposed to create_room which likely handles private rooms). It does not explicitly mention alternatives or when not to use, but the context is clear enough for an agent to infer the distinction.

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?