Skip to main content
Glama

Read a backed-up chat

read_chat
Read-onlyIdempotent

Retrieves a specific chat backed up to Thread using its chat ID from search_chats, so you can review saved conversations.

Instructions

Read one chat the user backed up to Thread, using the chat id from search_chats.

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful prerequisite that the id comes from search_chats and that the chat must have been backed up, but it does not add further behavioral detail such as error handling or access constraints.

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?

It is a single tightly written sentence with the action and scope front-loaded, followed by the parameter source. Every phrase earns its place.

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 simple one-parameter read operation with annotations and an output schema, the description supplies the essential action and id source. It does not mention failure modes or whether any backed-up chat can be read, but those gaps are minor given the tool's simplicity.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It does so by clarifying that the `chat` parameter is an id obtained from search_chats rather than a name or search query, though it does not specify format or exact-match expectations.

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?

The description states a specific verb and resource: 'Read one chat the user backed up to Thread.' It also distinguishes this tool from the sibling search_chats by positioning it as the follow-up that takes a specific chat id.

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 clearly tells the agent to use the `chat` id from search_chats, which is explicit routing guidance to the right sibling. It does not state when not to use the tool or what to do if the chat is not found, but the intended usage context is clear.

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