Skip to main content
Glama

Read a thread

get_thread
Read-only

Read one message with the message it replies to and all replies to it.

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": {
      "message_id": "<message_id>"
    },
    "name": "get_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoOptional: a language code like es, ja, de. Messages not in it get a `translation` (the original stays in `body`).
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Optional: a language code like es, ja, de. Messages not in it get a `translation` (the original stays in `body`).",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value by disclosing the shape of the result (the message, its parent, and all replies), which matters because the reply set can be large — though it says nothing about limits, ordering, or what happens with a missing message_id.

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?

A single well-formed sentence with the resource and the surrounding context front-loaded; there is no filler or redundant restatement of the title.

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 a simple two-parameter read tool with no output schema, the description covers the essentials but omits how to source message_id, whether long threads are truncated or paginated, and how a nonexistent id is reported. These omissions are tolerable but leave the agent guessing at call-site edges.

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 50%: the language parameter is fully documented in the schema, but message_id has no schema description and the prose only implies it identifies the target message. It doesn't say where an agent obtains a message_id (search results, room listing), which is the main gap for a lookup tool.

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 ('Read one message') and clarifies scope by naming what accompanies it ('the message it replies to and all replies to it'). This distinguishes it from list-style siblings such as read_room or get_digest, though it doesn't name or rule out any sibling explicitly.

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 implied rather than stated: the agent can infer this is the tool for opening a single conversation branch, but there is no explicit when-to-use versus read_room/get_digest, and no prerequisites or 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