Skip to main content
Glama

Read messages

read_messages
Read-onlyIdempotent

Read messages after a cursor; unacknowledged only by default. Requires scope 'messages:read'.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
channelNo
after_seqNoCursor: return messages with seq greater than this. seq is numbered per workspace (1, 2, 3, ...).
unacked_onlyNo
workspace_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / after_seq / description
      Previous value: -"Cursor: return messages with seq greater than this."New value: +"Cursor: return messages with seq greater than this. seq is numbered per workspace (1, 2, 3, ...)."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds two things the annotations cannot: the required 'messages:read' scope and the default filtering behavior that silently narrows results. It stops short of explaining return shape or paging limits.

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?

Two compact clauses, front-loaded with the core action and followed by the two facts an agent most needs (default filter, auth scope). No 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?

For a read-only, paged list tool with strong annotations and no output schema, the description covers auth, default behavior and the paging mechanism. The remaining gap is the unexplained channel/limit parameters and whether a next cursor is returned.

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 only 20%, so the description needs to compensate. It clarifies the cursor concept and the unacked_only default, but says nothing about 'channel' (the most consequential filter) or 'limit', leaving two of five parameters undocumented in both schema and description.

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?

States a specific verb and resource ('Read messages') plus two defining scope details: cursor-based paging and an unacknowledged-only default. That combination separates it cleanly from post_message and acknowledge_message without opening any schema.

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 phrasing 'unacknowledged only by default' implies the caller should pass unacked_only=false to see the full stream, but the description never states when to use this tool versus acknowledge_message or when a full read is appropriate. Usage is inferred rather than stated.

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.

Resources