Skip to main content
Glama

forward_message

Destructive

Forward an email as plain text while preserving its subject, body, original text, and optional attachments; save as a draft unless confirm is true.

Instructions

Forward a message as plain text. The new message has the subject 'Fwd: ...', your 'body' (if any), a header block (From, Date, Subject, To) and the original text. The attachments of the original are included unless 'include_attachments' is false. An attachment that cannot be fetched or is above 25 MB is skipped, the result lists it, and the forward is saved as a draft even with 'confirm' true. 'attachments' adds more files. Forwarded attachments are copied to ~/Library/Caches/applesauce/attachments and kept for 24 hours. Without 'confirm' true nothing is sent: the message is saved as a draft. With more than one Mail account, 'from' must say which one sends. Ask the user when it is not clear. If Mail is not running, applesauce opens it hidden in the background and leaves it open. Sending cannot be undone.

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": {
      "id": "<id>",
      "to": "<to>"
    },
    "name": "forward_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCc addresses. Each must contain @.
idYesMessage id from search_mail.
toYesTo addresses. Each must contain @.
bccNoBcc addresses. Each must contain @.
bodyNoPlain text that goes above the forwarded message.
fromNoSender: an account name, or one address of an account (from list_accounts).
confirmNoMust be true to send.
in_accountNoAccount id of the message (the 'account_id' field of search_mail). Only needed with 'in_mailbox'.
in_mailboxNoMailbox path of the message (the 'mailbox' field of search_mail). Only needed when Full Disk Access is missing. Give 'in_account' too.
attachmentsNoAbsolute paths of files to attach. At most 10 files, 25 MB for each file and 25 MB in all. Folders, app bundles and files in secret folders (~/.ssh, ~/Library/Keychains and similar) are refused.
include_attachmentsNotrue to forward the attachments of the original. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond annotations, it discloses important behavior: the forwarded message is plain text with a Fwd subject and header block, original attachments are included by default, attachments over 25 MB or unfetchable are skipped and reported, forwarded attachments are cached for 24 hours, and sending cannot be undone. This is rich, safety-relevant context consistent with destructiveHint=true.

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?

The description is front-loaded and information-dense, moving from purpose to composition to edge cases and safety. It is longer than a minimal definition but most sentences carry operational value, with little repetition.

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 an 11-parameter destructive tool with no output schema, the description covers the critical behavior: draft fallback, attachment limits and caching, account selection ambiguity, Mail launch behavior, and irreversibility of sending. It is complete enough for an agent to invoke the tool safely.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all parameters. The description still adds useful meaning, especially that 'from' must identify the sending account when multiple accounts exist and that the user should be asked if it is ambiguous.

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 clearly states a specific verb and resource: forwarding an existing message as plain text, including the resulting subject/body/header structure. It does not explicitly name a sibling alternative such as create_draft, but the forwarding semantics are sufficiently distinct.

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?

The description gives concrete usage conditions: without 'confirm' true it saves a draft, with multiple Mail accounts 'from' must identify the sender, and the user should be asked when unclear. It does not explicitly compare with alternative tools, so it stops short of full alternative routing guidance.

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