Skip to main content
Glama

read_messages

Retrieves recent conversations from a Google Chat space or DM, returning each thread's first message and recent replies with attachments and links.

Instructions

Read the latest threads of a space or DM: each thread's first message plus its newest replies replies, with Drive files, attachments and links.

space_id and is_dm come from list_spaces; in every tool, is_dm may be left out and is then looked up. page_size is the number of threads. Use read_thread for every message of one thread.

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>"
    },
    "name": "read_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_dmNo
repliesNo
space_idYes
page_sizeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the return is a thread summary rather than full history, includes attachments/Drive files/links, and that is_dm is auto-resolved when absent. It does not mention ordering guarantees, pagination limits beyond page_size, or any auth/scope constraints, so it stops short of full behavioral disclosure.

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?

Content is front-loaded: what it returns first, then parameter provenance, then the alternative. The first sentence is overloaded with a line-broken clause ("each thread's first message plus its newest `replies` replies") which reads awkwardly, but no sentence is filler.

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?

Return shape is covered by the output schema, and the description adds the thread-vs-message distinction, parameter provenance and the read_thread alternative needed to call this correctly. Remaining gaps (defaults, ordering, pagination limits) are minor for a read-only listing tool with an output schema.

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 coverage is 0%, so the description must compensate, and it largely does: space_id's provenance is given (comes from list_spaces), is_dm's optionality and lookup behavior are explained, page_size is defined as "the number of threads," and `replies` is defined in context as the newest replies shown per thread. It omits the default values and the expected ID format, leaving a small gap against 0% schema coverage.

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?

States a specific verb and resource ("Read the latest threads of a space or DM") and immediately defines the exact granularity: each thread's first message plus its newest `replies` replies, including Drive files, attachments and links. It also names read_thread as the different alternative, so an agent can distinguish it without opening a schema.

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

Usage Guidelines5/5

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

"Use read_thread for every message of one thread" is an explicit when-not rule with the alternative named. It additionally tells the agent where space_id and is_dm come from (list_spaces) and that is_dm may be omitted and is then looked up, which is a real invocation prerequisite.

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