Skip to main content
Glama

smtp_send_message

Send a new email via SMTP with recipient, subject, body, and attachment previews; require explicit user confirmation before delivery.

Instructions

Send a new email via SMTP. Before calling, show the user a full preview (To, CC, BCC, subject, rendered body, attachments) and get explicit confirmation.

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

Input Schema

NameRequiredDescriptionDefault
ccNoCC recipients (optional, max 50)
toYesRecipient email addresses (1..50)
bccNoBCC recipients (optional, max 50)
subjectYesEmail subject (1..998 characters)
reply_toNoReply-To address (optional)
body_htmlNoHTML body (at least one of body_text or body_html required). Separate field from `body_text`: pass the HTML itself, never wrapped in pseudo-tags like `<body_html>`; the server rejects them.
body_textNoPlain text body (at least one of body_text or body_html required). Separate field from `body_html`: never concatenate the two or wrap content in pseudo-tags like `<body_text>`; the server rejects them.
account_idNoAccount identifier (defaults to `"default"`)default
referencesNoReferences header for threading (optional)
attachmentsNoFile attachments (optional, base64-encoded)
in_reply_toNoIn-Reply-To message ID for threading (optional)

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • changedInput schema / properties / body_html / description
      Previous value: -"HTML body (at least one of body_text or body_html required)"New value: +"HTML body (at least one of body_text or body_html required).\nSeparate field from `body_text`: pass the HTML itself, never wrapped\nin pseudo-tags like `<body_html>`; the server rejects them."
    • changedInput schema / properties / body_text / description
      Previous value: -"Plain text body (at least one of body_text or body_html required)"New value: +"Plain text body (at least one of body_text or body_html required).\nSeparate field from `body_html`: never concatenate the two or wrap\ncontent in pseudo-tags like `<body_text>`; the server rejects them."
  2. First observedv0.4.12

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag openWorld=true, idempotent=false, destructive=false, so safety profile is partially covered. The description adds the crucial behavioral requirement that every outbound field must be previewed and confirmed by the user before an irreversible external send, which is exactly the kind of context annotations cannot express. It stops short of explaining failure modes or what happens on partial delivery.

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, front-loaded with purpose and followed immediately by the required confirmation workflow. No filler or redundant restatement of the title.

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 an 11-parameter mutation tool with full schema coverage, an output schema, and annotations, the description covers purpose and the key safety workflow. Account selection, attachment size handling, and the body_text/body_html requirement are left entirely to the schema, which is acceptable but leaves minor gaps at the description level.

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 baseline is 3. The description enumerates To, CC, BCC, subject, rendered body, and attachments, which mirrors rather than extends the schema's own documentation; no additional syntax, limits, or threading guidance is supplied.

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 ('Send a new email via SMTP'), and the word 'new' implicitly separates it from the reply/forward siblings. It does not name the EWS/Graph send alternatives, so differentiation across backends is only partially achieved.

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?

Gives a concrete pre-call workflow (show a full preview and obtain explicit confirmation), which is real guidance on how to invoke it. It offers no guidance on when to choose SMTP over the sibling ews_send_message or graph_send_message, and no exclusions or prerequisites beyond the confirmation step.

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