Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

send_test_email

Destructive

Send a minimal diagnostic email to verify Proton Bridge SMTP credentials and connectivity before relying on standard sending. Returns delivery status and transport debug info.

Instructions

Send a minimal diagnostic email to confirm Proton Bridge SMTP credentials and connectivity. Use before relying on send_email in a new environment. Prefer get_connection_status for a connectivity check that does not actually send mail. Returns transport debug info and delivery status. Requires PROTONMAIL_ALLOW_SEND, and confirmed:true when PROTONMAIL_CONFIRM_DESTRUCTIVE is enabled; subject to PROTONMAIL_RESTRICT_OUTBOUND_TO_SELF like every other send path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient email address.
fromNoSend as this address instead of the Bridge login's default (e.g. an alias or additional address on the same Proton account). Proton accepts any address verified on the account; an address not on the account is rejected by Proton at send time.
confirmedNoSet to true to confirm this send when PROTONMAIL_CONFIRM_DESTRUCTIVE is enabled.
customMessageNoOptional custom test body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.37
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Send as this address instead of the Bridge login's default (e.g. an alias or additional address on the same Proton account). Proton accepts any address verified on the account; an address not on the account is rejected by Proton at send time.",
+  "type": "string"
+}
  2. Changed1 schema field changedv2.0.8
    • addedInput schema / properties / confirmed
      Added value: +{
+  "description": "Set to true to confirm this send when PROTONMAIL_CONFIRM_DESTRUCTIVE is enabled.",
+  "type": "boolean"
+}
  3. Addedv1.17.0
  4. Removedv1.13.11
  5. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond destructiveHint=true, the description discloses that the tool actually sends mail, returns transport debug info and delivery status, requires PROTONMAIL_ALLOW_SEND, and honors PROTONMAIL_CONFIRM_DESTRUCTIVE and PROTONMAIL_RESTRICT_OUTBOUND_TO_SELF. Side effects and conditional requirements are plainly stated.

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 dense sentences, front-loaded with core purpose before usage guidance and requirements. No filler; every clause contributes operational information.

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?

With no output schema, it supplies what the call returns (transport debug info and delivery status), and with only destructiveHint as annotation it also covers prerequisites, restrictions, and sibling routing. Nothing an agent needs to call this tool safely is missing.

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 coverage is 100%, so the schema already documents to, from, confirmed, and customMessage. The description adds non-obvious semantics for confirmed ('confirmed:true when PROTONMAIL_CONFIRM_DESTRUCTIVE is enabled') and clarifies that send restrictions apply to this path like every other, which is genuine value beyond the schema.

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 opens with a specific verb and resource: send a minimal diagnostic email to confirm Proton Bridge SMTP credentials and connectivity. It explicitly distinguishes itself from send_email and get_connection_status, so an agent can select it correctly even among many sibling tools.

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 gives concrete placement in a workflow ('Use before relying on send_email in a new environment') and names an explicit alternative when sending is not desired ('Prefer get_connection_status for a connectivity check that does not actually send mail'). This is clear when-to-use and when-not-to-use guidance.

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