Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

send_email

Destructive

Send an outbound email directly through Proton Mail Bridge SMTP. Supports attachments, Markdown, priority, read receipts, and a cancelable delay window for one-shot messages.

Instructions

Compose and send a new outbound email through Proton Bridge SMTP. Use for one-shot messages that need no review. Prefer create_draft when you want to save and review before sending, or reply_to_email when responding to an existing message. Fails if PROTONMAIL_ALLOW_SEND is false or if Bridge SMTP is unreachable. If PROTONMAIL_SEND_DELAY_SECONDS is set, this queues the send instead of sending immediately and returns a cancelable id — call cancel_send within the window to abort. Otherwise returns delivery confirmation immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCC recipient email addresses, comma-separated.
toYesRecipient email addresses, comma-separated.
bccNoBCC recipient email addresses, comma-separated.
bodyNoEmail body content (plain text). Required unless markdownBody is provided.
dryRunNoPreview the full recipient set and validate without sending.
isHtmlNoWhether body should be sent as HTML (ignored when markdownBody is provided).
replyToNoOptional reply-to email address.
subjectYesEmail subject.
fromNameNoOptional display name for the From header (e.g. 'Alice'). Does not change the sending address.
priorityNoSMTP priority header.
confirmedNoSet to true to confirm this irreversible send when PROTONMAIL_CONFIRM_DESTRUCTIVE is enabled.
attachmentsNoAttachments with base64 encoded content.
markdownBodyNoEmail body in Markdown. When provided, rendered to HTML with body as plain-text fallback; takes precedence over body+isHtml.
sanitizeHtmlNoStrip scripts, event handlers, and remote image beacons from HTML before delivery. Defaults to true when body is HTML.
appendSignatureNoAppend PROTONMAIL_SIGNATURE (if configured) to the body. Set false to send without it for this one message.
undoWindowSecondsNoOverride PROTONMAIL_SEND_DELAY_SECONDS for this one send: queue it for this many seconds (cancelable via cancel_send) instead of the server's configured default. 0 sends immediately even if the server has a default window configured. Same caveat as the server default: only fires while this server process stays running.
requestReadReceiptNoRequest a read receipt (MDN) via a Disposition-Notification-To header. Most mail clients ask the recipient before honoring it — this is a request, not a guarantee.
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only provide destructiveHint: true, but the description goes well beyond that. It discloses the failure when PROTONMAIL_ALLOW_SEND is false, the queueing behavior with PROTONMAIL_SEND_DELAY_SECONDS, cancellation via cancel_send, the same-process caveat, and the confirmation requirement for destructive sends. This is rich, useful context not present in structured fields.

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?

The description is dense but every sentence earns its place: purpose, usage boundary, failure conditions, delayed-send behavior, and fallback behavior. It is front-loaded with the core action and remains compact given the complexity of the tool.

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?

For a complex 17-parameter destructive send tool with only a destructiveHint annotation and no output schema, the description covers the essential behavior: what happens on success, failure modes, delay/cancellation, confirmation requirements, and relationship to sibling tools. It is complete enough 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?

Schema coverage is 100%, so the schema already documents all 17 parameters thoroughly. The description does not add additional parameter-level semantics beyond noting the delay override behavior, which is also described in the schema. Baseline 3 is appropriate because the schema carries the full burden.

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?

Description states a specific action ('Compose and send a new outbound email through Proton Bridge SMTP') with a clear resource and mechanism. It also distinguishes itself from siblings by calling out create_draft and reply_to_email, making the purpose unambiguous.

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?

Explicitly says when to use ('one-shot messages that need no review'), when not to, and names alternatives ('Prefer create_draft... or reply_to_email...'). Also provides operational guidance about failure conditions and delayed sends with cancel_send.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googlarz/proton-mail-bridge-client'

If you have feedback or need assistance with the MCP directory API, please join our Discord server