Skip to main content
Glama

mailroom_attachment

Download a single email attachment as base64, such as a PDF receipt, with an 8 MB size limit.

Instructions

Download one attachment from a message as base64 (for example a PDF receipt), up to 8 MB.

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": {
      "id": "<id>",
      "attachment": "<attachment>"
    },
    "name": "mailroom_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMessage id from mailroom_search (a numeric uid for Gmail/IMAP, a Graph id for Microsoft 365).
folderNoFolder: inbox (default), sent, drafts, trash, junk, archive, all, or a folder name.
accountNoWhich connected mailbox to use (its label from mailroom_accounts). Optional when only one is connected or a default is saved in memory.
attachmentYesAttachment id or file name as listed by mailroom_read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.8/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 behavioral burden. It usefully discloses the base64 return format and an 8 MB size cap, but it does not mention authentication needs, error behavior for oversized attachments, or whether the operation is strictly read-only.

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?

The description is a single front-loaded sentence with no wasted text. The example and size limit are compactly integrated and useful for invocation.

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?

For a tool with no output schema, the description states the return format (base64) and size limit, which are important for correct use. Schema descriptions cover the parameters, though the description could say more about account/auth context and failure modes.

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?

The input schema has 100% description coverage for all four parameters, so the schema already explains id, folder, account, and attachment. The description adds little parameter-specific meaning beyond indicating that a message and one attachment are involved.

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?

The description states a specific verb and resource: downloading one attachment from a message. It also specifies the output encoding (base64) and size limit, which clearly distinguishes it from siblings like mailroom_read that operate on message content rather than attachment payloads.

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 by the phrase 'Download one attachment from a message' and the PDF receipt example, but the description does not explicitly say when to choose this tool versus mailroom_read or mailroom_search. No exclusions or prerequisite workflow are stated.

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

Deploy Server

Other Tools