Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

reply_email

Sends an immediate reply to an email by UID, automatically setting recipients, subject, thread headers, and quoted text; supports reply-all and attachments.

Instructions

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

Recipients, "Re:" subject, thread headers and the quote are set
automatically. reply_all=True also replies to all CC (without yourself).

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>",
      "body_text": "<body_text>"
    },
    "name": "reply_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
folderNoINBOX
body_htmlNo
body_textYes
reply_allNo
attachmentsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it delivers the most important behavior: immediate, irreversible send plus an environment prerequisite. It also discloses the implicit side effects (recipients, "Re:" subject, thread headers, and quote set automatically) and reply_all CC semantics excluding yourself. It does not say whether the original is marked replied or a copy is stored in Sent, which are the remaining behavioral gaps.

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?

Front-loads the danger signal in caps before any detail, which is the right ordering for a destructive tool. Four short sentences with little waste, though the "keep this tool on 'ask every time'" host-config note is meta rather than tool semantics and slightly dilutes the parameter-relevant content.

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 described; the description covers the dangerous behavior, the prerequisite, and the auto-populated fields. It falls short on the attachments format (paths vs URLs?) and body_text vs body_html precedence, both of which an agent needs before composing a call.

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 and it only partly does: uid is explained as the target message and reply_all as "also replies to all CC (without yourself)". folder, body_text, body_html, and attachments get no explanation at all, leaving three of six parameters undocumented in both places.

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 (reply) and resource (email) plus the addressing key ("by uid"), which separates it from send_email, forward_email, and create_draft among the siblings. 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a hard precondition ("Only works with PROTON_SMTP_ENABLED=1") and an operational warning ("SENDS IMMEDIATELY - keep this tool on 'ask every time'") that function as when-to-use gates. It stops short of explicitly naming forward_email or create_draft as the alternative when the user wants review-before-send, so it is clear but not fully routing.

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