Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

get_thread

Displays a message's conversation chronologically by tracing References and Message-ID links in All Mail, letting you review related replies and context from one UID.

Instructions

Show the conversation/thread of a message (chronological).

Rebuilt from the References/Message-ID chain in 'All Mail' (not from the
subject). The returned uids refer to 'All Mail' - to read one:
get_email(uid, folder="All Mail").

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

Input Schema

NameRequiredDescriptionDefault
uidYes
limitNo
folderNoINBOX

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose genuinely non-obvious behavior: the thread is reconstructed from the References/Message-ID chain in 'All Mail', not from the subject line, and returned uids live in the 'All Mail' namespace. It does not say anything about read-only semantics, pagination via limit, or ordering of the returned collection beyond 'chronological'.

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?

Two short sentences, front-loaded with the purpose and the follow-up call, with no padding. The parenthetical and line breaks are slightly awkward but cost nothing in comprehension.

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 values need not be described, and the derivation from References/Message-ID is well covered. However, the description leaves an unresolved tension between 'returned uids refer to All Mail' and a `folder` parameter defaulting to INBOX, and it is silent on limit/pagination for a potentially long conversation.

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 description coverage is 0%, so the description must compensate and it only partially does: it clarifies that uids are 'All Mail' uids (important for the uid parameter) but never explains the `limit` parameter (default 50) or what the `folder` parameter (default INBOX) means for a tool that reports results from 'All Mail'. The uid namespace detail is real added meaning, but two of three parameters remain undefined.

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 ('Show the conversation/thread of a message') plus the ordering guarantee ('chronological'), and implicitly separates itself from get_email by noting that a returned uid must be read with get_email(uid, folder="All Mail"). An agent can tell what it returns without opening the schema.

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?

Usage is clear from context (retrieve a whole conversation rather than a single message) and the description supplies a concrete follow-up call for reading an individual message. There is no explicit 'do not use this when...' exclusion, so it stops short of the top band.

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