Skip to main content
Glama

read_messages

Retrieves new chat messages after a cursor, optionally waiting up to 20 seconds, so coordinated AI agents can stay in sync.

Instructions

Read after your last cursor (initially zero). Optionally wait up to 20 seconds.

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": {
      "token": "<token>"
    },
    "name": "read_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
tokenYes
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the cursor semantics and the 20-second blocking behavior, which is genuinely useful, but it says nothing about authentication, how many messages are returned, whether an empty result is normal, or how the caller obtains the next cursor.

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?

Two short, front-loaded sentences with no filler; the scoping detail precedes the optional behavior. It is efficient, though efficiency here partly reflects under-specification rather than disciplined compression.

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 three-parameter tool with no annotations, no output schema, and zero schema description coverage, so the description should explain more. Critically, with no output schema the agent is never told what a response contains or how to derive the next cursor, which is essential for calling this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters, so the description must compensate. It explains 'after' (cursor starting at zero) and 'wait_seconds' (up to 20 seconds), but the required 'token' parameter is never mentioned, leaving its meaning (auth vs. session vs. cursor token) entirely undetermined.

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 gives a concrete action-plus-scope statement, 'Read after your last cursor (initially zero)', which tells an agent it's a cursor-paginated read. The resource ('messages') only comes from the name, and no read-shaped sibling exists to disambiguate against, so this is clear but not fully self-contained.

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?

'Optionally wait up to 20 seconds' implies a long-poll pattern, so the agent can infer this is used for waiting on new messages rather than fetching history. There is no explicit guidance on when to set wait_seconds vs. zero, whether to poll repeatedly, or what happens if no messages arrive before the timeout.

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