Skip to main content
Glama

read_thread

Read all messages in a Google Chat thread, oldest first, or fetch only the newest messages by setting a limit. Use it to review conversation context before replying or searching.

Instructions

Read every message of one thread (or only its newest limit), oldest first.

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": {
      "space_id": "<space_id>",
      "thread_id": "<thread_id>"
    },
    "name": "read_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_dmNo
limitNo
space_idYes
thread_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses result ordering (oldest first) and that limit truncates to the newest N. It says nothing about pagination, permissions on a thread, what happens with an unknown thread_id, or how is_dm changes behavior.

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?

A single well-formed sentence with the ordering constraint front-loaded and no wasted words. Brevity comes at the cost of coverage, but no sentence is padding.

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?

An output schema exists, so return shape need not be described, and the ordering note covers the main result trait. However, for a tool with four parameters at zero schema coverage and no annotations, the definition is thinner than the surface area warrants.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description must compensate, but it only clarifies limit. space_id, thread_id, and especially the optional is_dm flag (whose effect on a DM thread is non-obvious) are left entirely to inference from their names.

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 every message of one thread) plus the ordering ('oldest first'), which an agent could not infer from the name. It does not distinguish itself from the sibling read_messages, so differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this versus read_messages, list_unread, or search_messages, and no prerequisites or exclusions. The only conditional in the text is about the limit parameter, not about tool selection.

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