Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

send_email

Sends a new email immediately via Proton Bridge SMTP with To/Cc/Bcc, attachments, and optional reply threading; use only when the message must be delivered now.

Instructions

Send a new email through Proton Bridge (SMTP). SENDS IMMEDIATELY and cannot be undone - keep this tool on "ask every time". Only works when the server was started with PROTON_SMTP_ENABLED=1.

to/cc/bcc comma-separated; attachments = local file paths. reply_to_uid
sets threading headers (reply_email/forward_email are usually better).

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": {
      "to": "<to>",
      "subject": "<subject>",
      "body_text": "<body_text>"
    },
    "name": "send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
subjectYes
body_htmlNo
body_textYes
attachmentsNo
reply_to_uidNo
reply_to_folderNoINBOX

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.8/5.0
Behavior5/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 it well: it declares the operation irreversible ('SENDS IMMEDIATELY and cannot be undone'), names the configuration requirement that makes it fail, and recommends a confirmation posture. The only omissions are SMTP error surface and rate limits, which are secondary given the output schema exists.

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?

Three short sentences with the dangerous behavior and the precondition front-loaded in caps, followed by parameter notes. Every sentence carries information an agent needs; no filler or restatement of the tool name.

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 9-parameter irreversible mutation with no annotations, the definition covers the safety profile, the enabling precondition, and the key parameter formats, and the output schema handles return values. The remaining hole is the relationship between body_text and body_html and how reply_to_folder is used, which an agent would want spelled out.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters, so the description must compensate, and it does for the ambiguous ones: recipient lists are comma-separated, attachments are local filesystem paths, reply_to_uid drives threading headers. Gaps remain for body_text vs body_html precedence and for reply_to_folder's role alongside reply_to_uid, both of which are left to inference.

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?

States a specific verb and resource ('Send a new email') plus the transport ('through Proton Bridge (SMTP)'), which distinguishes it from create_draft on one side and reply_email/forward_email on the other. An agent can identify the operation without opening the schema.

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?

Gives an explicit alternative and the condition that selects it: 'reply_to_uid sets threading headers (reply_email/forward_email are usually better)'. It also states a hard precondition ('Only works when the server was started with PROTON_SMTP_ENABLED=1') and a policy constraint ('keep this tool on ask every time'), which is more routing guidance than most definitions provide.

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