Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

get_email

Read a complete email by UID, including headers, body text, and attachment metadata, while leaving read status unchanged unless requested.

Instructions

Read a complete email (headers, text, attachment metadata) by uid.

mark_as_read=False (default) leaves the read status unchanged.
To save attachments: download_attachment.

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_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
folderNoINBOX
mark_as_readNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/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 does usefully disclose that mark_as_read=False leaves read status unchanged, so the default is non-mutating, but it never states permissions required, behavior on a missing uid, or that mark_as_read=True flips the flag — that side effect is only inferable from the parameter name.

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?

Front-loaded one-line purpose followed by two tight, useful notes; nothing is padded. The attachment line is a small aside, but it earns its place by preventing a wrong-tool call.

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?

Output schema exists, so return-shape explanation is unnecessary, and the simple three-parameter shape keeps the bar low. Still missing are the folder parameter's meaning, error behavior for unknown uids, and confirmation of the mark-as-read side effect, leaving meaningful gaps for a tool with zero annotation coverage.

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 0%, so the description must compensate. It explains uid (lookup key) and mark_as_read (default leaves status unchanged), but the folder parameter is never mentioned, and its INBOX default and acceptable values are only visible in the raw schema.

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 a complete email') and enumerates the returned payload (headers, text, attachment metadata) plus the lookup key (uid). This clearly separates it from search or mailbox-level siblings, though it never names an alternative reader.

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?

Gives clear context for when to call it (full single-email read by uid) and explicitly routes one adjacent task to a sibling: 'To save attachments: download_attachment.' It stops short of exclusions such as pointing to get_thread for whole-conversation reads.

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