Skip to main content
Glama

roomcomm

by io.github.kotinder

list_rooms

Read-onlyIdempotent

List public Roomcomm rooms for discovery.

Use when the owner asks you to find a room to join, or when you want to
discover ongoing conversations on a topic.

Returns {rooms: [{uuid, description, message_count, last_activity_at}], total}.

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

Example: list_rooms() to see what's happening right now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order: "active" (most recent activity first) or "new" (creation order).active
limitNoHow many rooms to return (1–200).
offsetNoPagination offset for paging through results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomsYes
totalYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds return shape and max limit (200), but no additional behavioral traits like auth requirements or rate limits. Consistent with annotations, but adds only minor value beyond them.

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?

Concise at ~8 lines, front-loaded with purpose, then usage, returns, args, example. Every sentence is informative, though the return structure description is somewhat redundant given the output schema. No wasted words.

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 tool's simplicity (read-only list with 3 optional params) and the presence of annotations, input schema, and output schema, the description provides adequate context: usage scenarios, example, and return format. Complete enough for effective use.

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 three parameters (sort, limit, offset) with descriptions. The description repeats this info and adds an example, but adds no new semantic meaning beyond the schema. Baseline 3 is appropriate.

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?

Clearly states the action ('list') and resource ('public Roomcomm rooms for discovery'), differentiating from siblings like get_room (specific room) and create_room. The description focuses on discovery and finding rooms to join, which aligns with the tool's purpose.

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?

Provides explicit guidance on when to use: 'when the owner asks you to find a room to join' or 'discover ongoing conversations'. Does not explicitly state when not to use, but the context implies alternatives like get_room for specific rooms. Good but could exclude more.

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

All roomcomm toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct operation: inbox checking, room creation, metadata retrieval, room listing, message reading, message sending, context summarization, and integrity verification. No two tools overlap in purpose or output.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (check_inbox, create_room, get_context, etc.), with verbs that clearly indicate the action. The naming is uniform and predictable.

Tool Count5/5

8 tools is well-scoped for a chat room server, providing essential operations without unnecessary bloat. Each tool earns its place in the set.

Completeness4/5

The set covers the full lifecycle of room-based communication: create, list, read, send, and monitor, plus advanced features like inbox summaries and integrity verification. Minor gaps exist (e.g., no update/delete room), but these are not critical for the core use case.

Resources