Skip to main content
Glama

read_chat

Read-onlyIdempotent

Browse messages from a single chat newest first, page through history with offset, and retrieve sender, reply, mention, and task-card details while skipping deleted placeholders by default.

Instructions

Messages of one chat (id or title), newest first by default.

Page back through history with offset (skip that many newest messages): offset=0 then offset=30, ... has_more says whether older messages exist. Messages carry sender names, reply_to ids, mentions, and task cards (type=task_card + task title). Deleted messages (which Mizito keeps as "." placeholders) are skipped unless include_deleted.

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": {
      "chat": "<chat>"
    },
    "name": "read_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
limitNo
offsetNo
oldest_firstNo
include_deletedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: newest-first default ordering, the has_more signal, the fact that Mizito stores deleted messages as '.' placeholders and that these are skipped unless include_deleted is set, and the shape of message content (sender names, reply_to ids, mentions, task cards). It still does not mention any rate limits, permissions, or truncation behavior on very long chats.

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 key behavior (what it returns, ordering, pagination) is front-loaded in the first two sentences, and the message-structure notes follow. It is dense but every clause carries information. Minor cost: it is written as sentence fragments with parenthetical asides, which reads a bit clipped but does not obscure meaning.

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?

An output schema exists, so the description is not obliged to enumerate return fields, and annotations cover the safety profile; given that, this is close to complete for a read tool with offset pagination. The residual gaps are the unexplained limit parameter and the absence of any fallback advice when the chat is not identifiable by id or title. For a five-parameter read tool it is adequate to good.

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?

With 0% schema description coverage, the description carries the burden for five parameters, and it partially does: offset is explained concretely ('skip that many newest messages'), include_deleted is explained via the placeholder note, oldest_first is implied by 'newest first by default', and chat is noted as accepting an id or a title. limit, however, gets no explanation at all — no maximum, no effect on has_more — which is a real gap at this coverage level.

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 opening clause names a specific resource and scope: 'Messages of one chat (id or title), newest first by default.' An agent can tell this reads messages from a single chat, which contrasts with the search/list siblings. The phrasing is a noun fragment rather than a verb phrase, and it never names a sibling to route against, so it stops short of a 5.

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?

It gives solid in-tool guidance on paging (offset=0, offset=30, 'has_more' signals older messages) and on when deleted messages appear. What's missing is guidance on when to choose this over search_chat or list_chats, e.g. whether search_chat is the right call when the chat id is unknown or the content is not the target. Usage is implied by the pagination walkthrough rather than stated as selection criteria.

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