Skip to main content
Glama

smtp_reply_message

Reply to an existing email via SMTP while automatically fetching the original to set proper threading headers (In-Reply-To, References, Re: subject).

Instructions

Reply to an existing message via SMTP (fetches original for proper threading). 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>",
      "body_text": "<body_text>"
    },
    "name": "smtp_reply_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
body_htmlNoReply body (HTML, optional). Separate field from `body_text`: pass the HTML itself, never wrapped in pseudo-tags like `<body_html>`; the server rejects them.
body_textYesReply body (plain text). Separate field from `body_html`: never concatenate the two or wrap content in pseudo-tags like `<body_text>`; the server rejects them.
reply_allNoReply to all recipients (default: false, reply to sender only)
account_idNoAccount identifier (defaults to `"default"`)default
message_idYesStable message ID of the message to reply to
attachmentsNoAdditional file attachments (optional, base64-encoded)
include_original_attachmentsNoInclude original email's attachments in the reply (default: false)

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: -"Reply body (HTML, optional)"New value: +"Reply body (HTML, optional).\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: -"Reply body (plain text)"New value: +"Reply body (plain text).\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.2/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and non-idempotent, but the description adds real context: it performs an IMAP fetch of the original to build In-Reply-To/References/Re: headers, and it mandates user confirmation before dispatch. It stops short of noting that a sent reply cannot be recalled or what happens if the original message is missing, which would be valuable for an outbound-irreversible action.

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, zero padding. The core action is front-loaded and the mandatory confirmation step follows immediately, so an agent can act on the first clause and still catch the guardrail.

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?

An output schema exists, so return values need no explanation, and the parameters are fully described in the schema. The description covers the threading mechanism and the confirmation gate, which are the non-obvious behaviors. Minor gap: no guidance on failure modes (original not found, account mismatch) for what is an outbound send.

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 every parameter is already documented, including the body_text/body_html separation and attachment sourcing. The description adds no parameter-level detail beyond the schema — the preview list of fields implies reply_all and attachments but does not explain them. Baseline 3 is appropriate.

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 ("Reply to an existing message via SMTP") and adds the distinguishing mechanism (fetches the original for proper threading). The verb "reply" cleanly separates it from the sibling send/forward tools without needing to name them.

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?

Gives an explicit pre-call workflow: show a full preview (To, CC, BCC, subject, rendered body, attachments) and obtain explicit user confirmation. What it lacks is any stated alternative or exclusion — e.g., when to prefer smtp_forward_message or smtp_send_message — so routing between siblings is left to inference.

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