Skip to main content
Glama

smtp_forward_message

Forward an existing email via SMTP by previewing To/CC/BCC, subject, body, and attachments, then requiring explicit user confirmation.

Instructions

Forward an existing message 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": {
      "message_id": "<message_id>",
      "to": "<to>"
    },
    "name": "smtp_forward_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesForward recipients (1..50)
body_htmlNoOptional cover note (HTML). Unlike `body_text`, this is sent as-is — the original message is NOT auto-quoted into the HTML part. If you need an HTML forward with the original embedded, compose it yourself and use `smtp_send_message`. Separate field from `body_text`: pass the HTML itself, never wrapped in pseudo-tags like `<body_html>`; the server rejects them.
body_textNoOptional cover note (plain text). The original message is appended below as a quoted block. 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
message_idYesStable message ID of the message to forward

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: -"Optional cover note (HTML). Unlike `body_text`, this is sent as-is\n— the original message is NOT auto-quoted into the HTML part. If you\nneed an HTML forward with the original embedded, compose it yourself\nand use `smtp_send_message`."New value: +"Optional cover note (HTML). Unlike `body_text`, this is sent as-is\n— the original message is NOT auto-quoted into the HTML part. If you\nneed an HTML forward with the original embedded, compose it yourself\nand use `smtp_send_message`.\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: -"Optional cover note (plain text). The original message is appended\nbelow as a quoted block."New value: +"Optional cover note (plain text). The original message is appended\nbelow as a quoted block.\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

A4.1/5.0
Behavior4/5

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

The annotations already disclose a non-read-only, open-world, non-idempotent send operation, and the description adds an important behavioral guardrail not captured there: mandatory user preview and explicit confirmation before sending. It does not describe error handling, rate limits, or authentication needs, but the confirmation requirement materially improves safe invocation.

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 sentences, both necessary, with the action stated first and the confirmation requirement immediately after. There is no redundant or filler wording.

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?

For a send operation with annotations, a complete input schema, and an output schema, the description supplies the essential purpose and the critical pre-send confirmation workflow. Parameter and return details are adequately covered by the structured data, so no important invocation guidance is missing.

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 description coverage is 100%, so the input schema already documents all five parameters in detail, including the distinction between body_html and body_text. The description adds no parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

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?

The description states a specific verb and resource: "Forward an existing message via SMTP." It is clearly distinct from sending or replying in practice, but it does not explicitly name sibling alternatives such as smtp_send_message or smtp_reply_message, so it falls short of full sibling differentiation.

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

Usage Guidelines4/5

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

It gives a clear pre-call workflow: show a full preview listing recipients, subject, rendered body, and attachments, then obtain explicit confirmation. It does not explicitly state when to choose this over smtp_send_message or smtp_reply_message, leaving that routing to the schema notes and inference.

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