Skip to main content
Glama
combor

Baryon MCP

get_thread

Read-onlyIdempotent

Read an entire email conversation from a single message, ordered oldest first. Gather replies from all folders via All Mail search, returning message IDs and optional trimmed bodies.

Instructions

Read a whole conversation from one of its messages, oldest first. Returns each message's envelope and message_id, and with include_bodies a shortened body for each. A conversation is usually split across folders, with your own replies in Sent, so pass the All Mail folder as search_folder to gather all of it. Use the returned uid and uidvalidity with get_email for a message in full.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesmessage uid from list_emails or search_emails
folderYesfolder name, as returned by list_folders
uidvalidityYesuidvalidity value returned alongside the uid; detects stale uids
search_folderNofolder to gather the conversation from; defaults to folder. Pass the All Mail folder to include replies filed elsewhere, such as your own in Sent
include_bodiesNoalso return each message's body, trimmed far shorter than get_email returns

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesmessages in the conversation before the return limit
folderYesfolder the conversation was gathered from; the uids below belong to it
messagesYesoldest first
returnedYes
uidvalidityYesgeneration of folder, to pass alongside a uid
Behavior5/5

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

Goes beyond the readOnly/idempotent annotations by disclosing ordered output (oldest first), folder-splitting behavior, include_bodies shortening, and how to chain results with get_email. This adds substantial behavioral context without contradicting the annotations.

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?

Three sentences, each earning its place: purpose, return payload, and practical usage caveat. Front-loaded and free of wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a rich output schema and strong annotations, the description covers ordering, folder behavior, optional body trimming, and integration with get_email. It is fully sufficient for an agent to invoke correctly.

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 100% with each parameter well-described. The description adds contextual usage (e.g., why search_folder matters) but does not introduce new parameter semantics beyond what the schema already provides, so baseline 3 is appropriate.

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 opens with 'Read a whole conversation from one of its messages, oldest first,' which clearly states the verb and resource. It distinguishes itself from siblings like get_email (single message) and search_emails (search) by focusing on thread retrieval.

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?

Provides clear usage context: pass the All Mail folder as search_folder to gather replies split across folders, and use get_email for full message bodies instead of shortened ones. However, it does not explicitly state when not to use this tool, so it stops short of full exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/combor/baryon-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server