Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

create_draft

Compose and save a new email draft to the Drafts folder without sending it, with recipients, subject, text or HTML body, and optional local file attachments.

Instructions

Create a draft in the Drafts folder without sending it.

to/cc comma-separated; attachments = local file paths.

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": "create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
subjectYes
body_htmlNo
body_textYes
attachmentsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does state the draft lands in the Drafts folder and is not sent, which is the core behavior, but it says nothing about side effects, whether attachments must exist on disk, whether duplicates are created, or permission/auth requirements for a mutation tool.

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?

Two short sentences, front-loaded with the primary purpose, with zero filler. It is efficient, though the second sentence reads as an afterthought fragment rather than structured guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema means return values need no explanation, and the core create-a-draft action is clear. However, for a six-parameter mutation tool with no annotations and no schema descriptions, gaps around body_html vs body_text and attachment path constraints leave it only minimally complete.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, so the schema names alone must carry meaning. The description adds format hints for only two fields (to/cc comma-separated, attachments as local file paths) and leaves subject, body_text, and the body_html/body_text relationship entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 draft) and locates it in the Drafts folder, with the key differentiator "without sending it" separating it from send_email. It stops short of naming siblings explicitly, but the scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

"Without sending it" implicitly signals when to pick this over send_email, but there is no explicit when-to-use or when-not-to-use guidance, and no mention of preconditions such as a valid connection or existing mailbox.

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