privateemail-mcp

send_email

Sends a new email from the connected mailbox and saves a copy in Sent. Use it only when the user explicitly requests this exact message; it cannot be undone.

Instructions

Send a new email from the connected mailbox and save a copy in Sent. This is outward-facing and cannot be undone: only call it when the user has asked for this exact message. To answer an existing message use reply_to_message instead, which threads and quotes correctly.

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>",
      "text": "<text>"
    },
    "name": "send_email"
  }
}

Input Schema

Name	Required	Description
`cc`	No
`to`	Yes
`bcc`	No
`html`	No	Optional HTML body
`text`	Yes	Plain-text body
`subject`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description still discloses the key traits: outward-facing, irreversible ('cannot be undone'), and a side effect (copy saved in Sent), plus a safety guard on caller intent. It omits error/validation behavior (e.g., invalid addresses) and doesn't state auth or recipient-level copy semantics, so it's strong but not complete.

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?

Two tight sentences: action+s side effect front-loaded, then the irreversibility warning, then the alternative. Every sentence carries information; zero waste.

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?

For a 6-param mutation with no output schema and no annotations, it covers purpose, safety, and the key sibling alternative well. Remaining gaps are parameter-level (e.g., cc/bcc/html usage) which the description never addresses.

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 only 33% and the description mentions no parameters at all — nothing about to/cc/bcc/subject/text/html or the to/cc/bcc distinction. It must compensate for the low coverage but doesn't, though the schema's formats and constraints provide some structural assistance.

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+resource+S effect: 'Send a new email from the connected mailbox and save a copy in Sent.' Explicitly distinguishes itself from reply_to_message, so an agent can differentiate it from its siblings 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 Guidelines5/5

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

Gives an explicit gating condition ('only call it when the user has asked for this exact message') and names the alternative (reply_to_message) with the reason (threads and quotes correctly). When, when-not, and alternative are all present.

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

Deploy Server