Skip to main content
Glama

read_email

Read-only

Retrieve a single Proton Mail message by UID from a folder without changing its read status; use UIDs from email listing or search.

Instructions

Read one email by its uid (from list_emails/search_emails, in the same folder). Does not mark it as read.

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": "read_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
folderNoINBOX
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful side-effect note ('Does not mark it as read'), but says nothing about truncation behavior from max_chars or what happens when the uid/folder combination is invalid.

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?

Two short sentences, zero filler, with the identity of the tool front-loaded and the side-effect caveat second. Nothing could be cut without losing information.

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?

With no output schema, the description should hint at what comes back — particularly that long bodies may be truncated at max_chars — and it does not. For a simple single-item read tool this is adequate but leaves a real gap around the truncation parameter.

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 does so for uid (its origin and same-folder constraint). The folder parameter and max_chars (default 20000, implying body truncation) are left entirely unexplained.

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 one email by its uid') and scopes it to a single message, which cleanly separates it from the plural siblings list_emails and search_emails. An agent can tell what this 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?

Explains the prerequisite for the key input: the uid must come from list_emails/search_emails and must be used with the same folder. It does not state when-not to use it or what happens on a bad uid, but the calling context is clear.

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