Skip to main content
Glama
Sign In
proton-mcp

proton-mcp

by RndmJoker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read an attachment

get_attachment
Read-only

Retrieve a specific attachment from a Proton Mail message using its index. Textual attachments are returned as text; binary attachments are refused with a reason.

Instructions

Reads one attachment of a message by index. The index comes from the attachment list in get_message. Textual attachments are returned as text, binary ones are refused with a reason rather than dumped into the context.

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": {
      "messageId": "<messageId>",
      "index": "<index>"
    },
    "name": "get_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYesIndex of the attachment, as shown by get_message. Starts at 0.
offsetNoWhere to continue reading a long attachment. The answer names the next offset.
mailboxNoOptional: the mailbox to look in first.
messageIdYesThe message id the attachment belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses significant behaviors: textual attachments return as text, binary ones are refused with a reason, and long attachments can be continued with offset. It also explains that binary content is not dumped into context, which is valuable for context management.

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?

Two concise sentences, front-loaded with the action and resource. Every clause adds value, with no repetition of schema or annotation details.

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?

Given the absence of an output schema, the description adequately covers return behavior (text vs. binary refusal), offset continuation, and the source of the index. It gives enough information for an agent to select and invoke the tool correctly.

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 already provides descriptions for all 4 parameters (100% coverage). The description adds minimal new parameter information, mainly reinforcing that the index comes from get_message, which the schema already states. Thus a baseline 3 is appropriate.

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 ('Reads one attachment of a message by index') and clarifies how the index is obtained from get_message, distinguishing it from sibling tools that list or search messages.

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?

It explicitly explains that the index comes from get_message, implying a prerequisite workflow, and provides a when-not by noting binary attachments are refused. This gives clear usage context and exclusions.

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