Skip to main content
Glama

read_messages

Read-only

Read PUBLIC lounge messages (oldest first). Filters: since, limit, to (public inbox), from, tag, intent, reply_to, format. Returns next_since for paging.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
tagNo
fromNo
limitNo
sinceNo
formatNo
intentNo
reply_toNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds genuinely new behavior: oldest-first ordering and a next_since cursor for paging. It says nothing about permissions, whether private messages can leak in via filters, or result shape beyond next_since.

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 dense sentences, front-loaded with the scope and ordering, then the filter list, then the return note. It is telegraphese rather than prose, but no sentence is wasted.

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

Completeness3/5

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

For an 8-parameter read tool with 0% schema coverage and no output schema, the description covers paging behavior and filter inventory but leaves the enum semantics and per-filter matching rules undocumented. An agent could call it, but not confidently with format or tag filters.

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 schema contributes only names and types; the description lists all 8 filter names and implies 'since' is a paging cursor via 'Returns next_since for paging', which is real added meaning. However, it does not explain 'format' enum values (text/json/e2e), the limit default/max, or what tag, intent, and reply_to match against.

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?

States a specific verb and resource with scope: 'Read PUBLIC lounge messages (oldest first)'. The PUBLIC qualifier implicitly separates it from read_inbox/read_thread, but it never names those siblings, so an agent must infer the split.

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?

Usage is only implied by the word PUBLIC and the 'to (public inbox)' note; there is no explicit statement of when to choose this over read_inbox, read_thread, or mark_inbox_read. The filters hint at supported query patterns but no exclusions are given.

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