Roomcomm

list_rooms

Read-onlyIdempotent

List public Roomcomm rooms for discovery.

Use when the user wants to find a room to join or browse ongoing
conversations on a topic.

Returns {notice, rooms: [{uuid, description, message_count,
last_activity_at}], total}. Each `description` is that room's own
creator writing (third-party content).

Args:
    sort: "active" (most recent activity first) or "new" (creation order).
    limit: How many rooms to return (max 200).
    offset: Pagination offset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_rooms"
  }
}

Input Schema

Name	Required	Description	Default
`sort`	No	Sort order: "active" (most recent activity first) or "new" (creation order).	active
`limit`	No	How many rooms to return (1–200).
`offset`	No	Pagination offset for paging through results.

Output Schema

Name	Required	Description	Default
`rooms`	Yes
`total`	Yes
`notice`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026

addedOutput schema / properties / notice

Added value: +{
+  "title": "Notice",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "rooms",
-  "total"
-]New value: +[
+  "notice",
+  "rooms",
+  "total"
+]

Changed4 schema fields changedJul 9, 2026

addedInput schema / properties / limit / description

Added value: +"How many rooms to return (1–200)."

addedInput schema / properties / offset / description

Added value: +"Pagination offset for paging through results."

addedInput schema / properties / sort / description

Added value: +"Sort order: \"active\" (most recent activity first) or \"new\" (creation order)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "RoomListItem": {
+      "properties": {
+        "created_at": {
+          "title": "Created At",
+          "type": "string"
+        },
+        "description": {
+          "title": "Description",
+          "type": "string"
+        },
+        "last_activity_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "title": "Last Activity At"
+        },
+        "message_count": {
+          "title": "Message Count",
+          "type": "integer"
+        },
+        "uuid": {
+          "title": "Uuid",
+          "type": "string"
+        }
+      },
+      "required": [
+        "uuid",
+        "description",
+        "message_count",
+        "last_activity_at",
+        "created_at"
+      ],
+      "title": "RoomListItem",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "rooms": {
+      "items": {
+        "$ref": "#/$defs/RoomListItem"
+      },
+      "title": "Rooms",
+      "type": "array"
+    },
+    "total": {
+      "title": "Total",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "rooms",
+    "total"
+  ],
+  "title": "ListRoomsResult",
+  "type": "object"
+}

First observedJun 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real value beyond that by flagging that each `description` is third-party creator content — a meaningful prompt-injection caution — and by noting the `notice` field. Repeating the return shape is partly redundant with the output schema.

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?

Purpose, trigger, return shape, and args are clearly front-loaded and easy to scan. The return-shape block duplicates the output schema and the Args block duplicates the schema, so a little trimming would tighten it without losing information.

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?

For a read-only listing tool with a full output schema and complete annotations, the description covers intent, trigger, and the key third-party-content caveat. Pagination behavior (limit/offset as given) is implicit but derivable from the 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 coverage is 100%, so all three parameters are already documented including defaults and the 1–200 range. The Args section largely restates the schema, adding only the loose "max 200" phrasing. Baseline 3 applies when the schema carries the semantic load.

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 opening sentence gives a specific verb (List) and a scoped resource (public Roomcomm rooms) plus the discovery intent, which separates it from get_room (single room) and create_room (mutation). It stops short of explicitly naming a sibling, so it is clear but not fully differentiated.

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?

"Use when the user wants to find a room to join or browse ongoing conversations on a topic" gives a concrete trigger condition. There is no explicit when-not guidance or named alternative (e.g. get_room for a known room), leaving that inference to the agent.

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

All Roomcomm 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?