Skip to main content
Glama

Mail Get Email

mail_get_email

Retrieve a single Apple Mail message by ID, including full body content and attachments, to inspect or process an email in detail.

Instructions

Single email with full content + attachments (disk-first ~3ms).

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": {
      "message_id": "<message_id>"
    },
    "name": "mail_get_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 add genuinely useful behavioral context — that content and attachments are included and that reads are disk-backed at ~3ms — which helps an agent gauge cost. It is silent on the traits that matter most for an unannotated tool: whether fetching marks the message as read, what happens with an invalid or missing message_id, and any auth/permission requirements.

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?

One short sentence, front-loaded with the key noun and return contents, with the latency note trailing as parenthetical. No wasted words, though the extreme compression leaves no room for usage or parameter detail.

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?

The tool is simple (1 required param) and has an output schema, so the description needn't document return shape — and it still gives a useful summary of what comes back. However, for an unannotated mail-fetch operation it omits side effects (read status) and error behavior on a bad ID, leaving meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single message_id parameter, so the description must compensate and does not. It never states that message_id identifies the email, nor the expected format (ID vs RFC Message-ID header), which is a real ambiguity an agent could trip on.

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?

"Single email with full content + attachments" identifies the resource and its scope precisely; the word "Single" implicitly contrasts with the plural sibling mail_get_emails. The verb is elided (no "retrieve"/"fetch"), so it reads as a label rather than an action, but an agent can still tell what it returns.

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

Usage Guidelines3/5

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

No explicit when-to-use statement, no prerequisites, no named alternative. The only guidance is implied by "Single" versus the sibling mail_get_emails list tool — enough to infer the choice for a one-message lookup, but nothing about batch vs single or when the extra cost (attachments, full body) is warranted.

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