Skip to main content
Glama
s-morgan-jeffries

apple-mail-mcp

get_attachment_content

Read-onlyIdempotent

Read attachment content inline without saving to disk. Inspect text files, JSON, or small PDFs during email triage workflows.

Instructions

Read one attachment's content inline, without writing it to disk.

For "triage" workflows where you want to inspect an attachment (a text file, JSON, a small PDF) before deciding what to do with it — instead of save_attachments → read the file → clean up.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoMail.app account name or UUID. Supply it (with ``mailbox``) to use the faster IMAP path; pass the same value you read the message with so the attachment ordering matches.
mailboxNoFolder the message lives in (for the IMAP path).
message_idYesMessage id, as returned by ``search_messages`` / ``get_messages`` (RFC 5322 Message-ID on the IMAP path, Mail's internal id on the AppleScript path).
attachment_indexYes0-based index into the message's attachments, in the same order ``get_attachments`` / ``get_messages`` (``include_attachments=True``) report them.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that it reads inline without writing to disk, reinforcing the non-destructive nature and providing additional I/O behavioral context. No contradiction.

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 sentences plus a short paragraph. Front-loaded with the main purpose. Slightly verbose in the second part but overall efficient and well-structured.

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

Completeness4/5

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

Given the presence of an output schema (not shown but indicated) and good annotations, the description covers usage context (triage workflows) and alternatives. For a 4-parameter tool with 2 required, it is fairly complete.

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 100%, with each parameter described in the input schema. The tool description does not add additional meaning beyond what is already in the schema, so baseline 3 applies.

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?

Description states 'Read one attachment's content inline, without writing it to disk.' This is a specific verb+resource, and it distinguishes from sibling 'save_attachments' by clarifying inline reading vs. file saving.

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

Usage Guidelines5/5

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

Explicitly says to use for 'triage' workflows to inspect an attachment before deciding what to do, contrasting with the alternative workflow of saving, reading, then cleaning up. This provides clear when-to-use and when-not-to-use guidance.

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/s-morgan-jeffries/apple-mail-fast-mcp'

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