Skip to main content
Glama

rooms

Join, leave, or list encrypted real-time chat spaces and read message history newest page first, using a cursor to fetch older messages.

Instructions

Join, leave or list rooms, or read a room's history: the newest page first, its messages oldest first, and before (the cursor a page names when older messages exist) reads the page older than it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "rooms"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomNo
limitNo
actionYes
beforeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses history ordering and cursor behavior, but it does not describe side effects of join/leave, permissions, failure modes, or required action/parameter combinations.

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?

The definition is compact and front-loaded with the available actions. The pagination clause is dense and slightly awkward, but every part contributes needed meaning.

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

Completeness2/5

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

This is a multi-action tool with no annotations and no output schema, yet the description does not cover required room/action combinations, limit semantics, join/leave effects, or what a history response looks like. It handles pagination well but leaves significant operational gaps.

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 0%, so the description must compensate. It clarifies the action values and defines 'before' as a cursor for older pages, but 'room' and especially 'limit' remain unexplained beyond the schema's types and bounds.

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 names four concrete operations (join, leave, list, history) on rooms, so an agent can identify the resource and actions. It is slightly ambiguous about how the internal 'history' action relates to the sibling tool named 'history', but the overall purpose is clear.

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

Usage Guidelines3/5

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

The actions imply when each mode is used, and the description explains history pagination with 'before'. However, it gives no explicit guidance on choosing this tool over siblings or on prerequisites such as whether history requires joining first.

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

Deploy Server

Other Tools