Skip to main content
Glama

lobby_read

Read-only

Mandate Lobby: read room messages newer than a cursor (poll with the returned cursor).

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": {
      "room": "<room>"
    },
    "name": "lobby_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomYesRoom name to read, e.g. general (see lobby_rooms).
limitNoOptional maximum number of messages to return (1-200, default 50).
sinceNoOptional cursor from a previous response; returns only newer messages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Optional maximum number of messages to return (1-200, default 50)."
    • addedInput schema / properties / room / description
      Added value: +"Room name to read, e.g. general (see lobby_rooms)."
    • addedInput schema / properties / since / description
      Added value: +"Optional cursor from a previous response; returns only newer messages."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No contradictions with the `readOnlyHint` annotation exist. The description adds useful operational context by specifying the cursor-based retrieval, which informs the agent about the tool's stateful nature.

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 single sentence is perfectly constructed, front-loading the core function and immediately explaining its primary operational constraint (cursor/polling) without any unnecessary filler.

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 that the parameters are 100% documented, the definition is quite complete for a retrieval task. It gives the agent enough operational context to decide when and how to use this time-sensitive polling function.

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?

Since schema description coverage is 100%, the baseline is a 3. The description reinforces that the primary input is the 'room' and the filtering is done via the 'cursor,' which aligns with the structure but adds little semantic depth beyond the schema.

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 clearly identifies the action (read room messages) and the context (Lobby). It is distinct from sibling tools like `lobby_send` or `lobby_post` by focusing on the retrieval mechanism.

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?

It provides a specific workflow instruction by stating that the tool is designed for polling: '(poll with the returned cursor).' This tells the agent *how* to use the tool over time, distinguishing it from a single snapshot read.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.