Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

download_attachment

Save attachments from a Proton Mail message by UID to local disk, with optional filename, index, folder, and save directory controls; path traversal is blocked.

Instructions

Save the attachment(s) of a message (by uid) to local disk.

Without filename/index and with several attachments, the available ones
are listed first. save_dir defaults to ~/Downloads/proton-mail-mcp; path
traversal is prevented.

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

Input Schema

NameRequiredDescriptionDefault
uidYes
indexNo
folderNoINBOX
filenameNo
save_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

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 burden and does disclose useful traits: files land on local disk, save_dir defaults to ~/Downloads/proton-mail-mcp, and path traversal is prevented. It omits what happens when a file with the same name already exists, whether writes are reversible, and any 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?

Three short lines, front-loaded with the core action and followed by the two caveats an agent needs. The phrasing is terse to the point of being slightly compressed ('Without filename/index'), but nothing is wasted.

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

Completeness5/5

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

An output schema exists, so return values need no explanation, and the description covers the download target, default location, the listing fallback, and the path-traversal safeguard. What remains missing (the folder parameter, overwrite behavior) is modest for a single-purpose attachment saver.

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; it covers uid, filename, index (implicitly via the listing behavior) and the save_dir default, but never explains the folder parameter (default INBOX) nor how filename matching behaves if the name is wrong.

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?

States a specific verb and resource: save a message's attachments to local disk, keyed by uid. It is clearly distinct from retrieval tools like get_email, though it never names a sibling explicitly.

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?

Gives concrete conditional guidance: with several attachments and no filename/index, the tool lists available attachments first rather than downloading, which tells the agent to expect a two-call workflow. It doesn't state when to prefer filename over index or when not to use this tool at all.

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