Skip to main content
Glama
combor

Baryon MCP

save_draft

Destructive

Create a complete Proton Mail draft with plain text, optional HTML, and attachments. Provide an existing draft UID and UIDVALIDITY to replace it.

Instructions

Create a complete Proton Mail draft, or replace an existing draft when uid and uidvalidity are provided. Supports plain text, an optional HTML alternative, and bounded attachments supplied either inline as base64 (content_base64) or as a path inside the server's attachment directory that it reads at save time (content_path). To answer one message, save_reply_draft derives its recipients and threading for you. To reply inside a thread here, read the message with get_email and set in_reply_to to its message_id, and references to its references followed by its message_id; when it reports no references, use its in_reply_to in their place so earlier ancestry survives. A replacement keeps the previous draft's Message-ID, plus whichever of its In-Reply-To and References the call omits; passing an empty array for either removes it, detaching the draft from its thread. Updating appends the replacement before removing the old UID; inspect warning if cleanup was incomplete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCc recipient addresses
toNoTo recipient addresses
bccNoBcc recipient addresses retained in the saved draft
uidNoexisting draft UID to replace; requires uidvalidity
fromYessender address; must be one of the Proton account addresses exposed by Bridge, which list_sender_identities reports
subjectNo
html_bodyNooptional HTML alternative, up to 50000 characters
text_bodyNoplain-text body, up to 50000 characters
referencesNoconversation chain: the parent email's references followed by its message_id; set together with in_reply_to so clients thread the reply; when replacing a draft, omit to keep the existing header or pass an empty array to remove it
attachmentsNoregular file attachments; at most 100 and 25 MB decoded in total
in_reply_toNoMessage-IDs this draft replies to, normally just the message_id of the email being answered; angle brackets optional; when replacing a draft, omit to keep the existing header or pass an empty array to remove it
uidvalidityNoDrafts UIDVALIDITY accompanying uid

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesUID of the newly saved draft
folderYes
warningNo
uidvalidityYesDrafts folder generation accompanying uid
replaced_uidNo
previous_draft_removedYes
Behavior5/5

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

The description goes well beyond the annotations: it explains that replacement preserves the previous draft's Message-ID and headers, that passing an empty array removes headers and detaches the draft, and that updates append before removing the old UID with a warning if cleanup is incomplete. It also discloses that content_path files are read at save time. These behaviors align with the destructiveHint and are not visible in the input schema.

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 long but each sentence carries distinct, decision-relevant information for an agent. The primary purpose is front-loaded, and the detailed threading and replacement semantics are organized in a logical sequence with no filler or repetition.

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?

Given the tool's complexity and presence of an output schema, the description is complete: an agent can correctly decide create vs. no replacement, serial composition for replies, attachment transport, and uid/UUID valid combination without opening the schema. No critical invocation decision is left implicit.

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

Parameters5/5

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

Even though schema coverage is 92%, the description adds meaning that the schema alone does not provide: uid requires uidvalidity for replacement, content_base64 and content_path are mutually exclusive, and threading fields follow the parent email's references plus message_id. This is substantial enrichment beyond the raw property descriptions.

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: 'Create a complete Proton Mail draft, or replace an existing draft when uid and uidvalidity are provided.' It also differentiates this tool from the sibling save_reply_draft by explaining which tool is meant for answering a single message.

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 explicit routing: 'To answer one message, save_reply_draft derives its recipients and threading for you,' and tells the agent exactly when and how to reply inside a thread with this tool by setting in_reply_to and references from get_email. It also covers replacement and attachment usage conditions, so the agent receives concrete yes/no selection guidance.

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

Install Server

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/combor/baryon-mcp'

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