Skip to main content
Glama

mail_attachment

Read-only

Read a single email attachment as text, converting PDF, Word, Excel, PowerPoint, and similar files for content extraction.

Instructions

Read one attachment as text (PDF, Word, Excel, PowerPoint and more are converted).

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>",
      "attachment_id": "<attachment_id>"
    },
    "name": "mail_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes
attachment_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description contributes one genuinely useful behavioral fact — that PDF, Word, Excel and PowerPoint content is converted to text — but says nothing about size limits, unsupported or encrypted files, or how failures surface.

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?

A single front-loaded sentence with no filler; the conversion parenthetical is the most decision-relevant detail and is included compactly. Minor vagueness in "and more" keeps it from being maximally tight.

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 and has both annotations and an output schema, so much of the burden is offloaded. Still missing is how to source the attachment_id and what happens with oversized or non-convertible attachments — gaps an agent would hit on first real use.

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 two required parameters, so the description carries the full burden and provides no meaning at all for message_id or attachment_id. It does not even indicate where an attachment_id comes from (presumably a message-detail call), leaving the agent to infer from parameter names alone.

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?

The description uses a specific verb ("Read") plus a precise resource ("one attachment") and states the return form ("as text"), including the notable fact that common binary formats are converted. That distinguishes it from a message-level reader like mail_get, though it does not explicitly name that sibling.

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?

Usage is implied rather than spelled out: an agent can infer to call this when it needs the contents of a specific attachment. There is no explicit when-not condition, no mention of a prerequisite lookup step to obtain the attachment_id, and no alternative named for cases such as listing attachments.

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