Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

forward_email

Forwards a selected email by UID to specified recipients immediately, adding the original subject prefix and quoted content, with optional CC and attachment inclusion.

Instructions

Forward an email (by uid). SENDS IMMEDIATELY - keep this tool on "ask every time". Only works with PROTON_SMTP_ENABLED=1.

"Fwd:" subject and quote block are automatic. to/cc comma-separated;
include_attachments=True also attaches the original attachments.

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>",
      "to": "<to>"
    },
    "name": "forward_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
uidYes
folderNoINBOX
body_htmlNo
body_textNo
attachmentsNo
include_attachmentsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so well: it flags immediate, irreversible sending, discloses the required environment configuration, and explains that the Fwd subject and quote block are generated rather than supplied. It omits any mention of sender/account scoping or failure modes when SMTP is disabled beyond the bare prerequisite.

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?

The highest-risk fact ("SENDS IMMEDIATELY") is front-loaded and every sentence adds information. The stray line breaks and trailing quote at the end slightly degrade readability but cost no real length.

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?

An output schema exists, so return values need not be explained, and the description covers the safety profile and the auto-generated content for a write tool with zero annotations. The gaps are the overlapping `attachments` versus `include_attachments` semantics and the body_text default, which matter for a mutation of this size.

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% across 8 parameters, so the description must compensate and only partially does: it clarifies comma-separated to/cc and that include_attachments=True pulls in the original's attachments. It says nothing about folder, body_text/body_html interaction with the automatic quote block, or how the separate `attachments` parameter differs from include_attachments, leaving the most ambiguous parameters undocumented.

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 states a specific verb and resource ("Forward an email (by uid)") plus the mechanism it applies automatically ("Fwd:" subject and quote block), so an agent can tell it apart from a plain send. It stops short of naming how it differs from reply_email or send_email, leaving that inference to the agent.

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?

The prerequisite "Only works with PROTON_SMTP_ENABLED=1" is genuine when-to-use guidance, and the caution to keep it on "ask every time" frames the risk. However, there is no guidance on when to choose forwarding versus reply_email or create_draft, so the routing decision is only implied.

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