Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

forward-message

Forward an existing email by ID to new recipients, with an optional prepended message. Set send=false to save as draft instead of sending immediately.

Instructions

Use when: forwarding an existing message (by id) to new recipients (to is an array), with an optional body to prepend. Set send=false to save as a draft. Returns: a confirmation that the message was forwarded or saved as a draft. Do not use when: replying to the sender/recipients (use reply-to-message) or composing a new message (use send-email / create-draft). Safety: with the default send=true this SENDS real email immediately and cannot be unsent — require explicit user confirmation of the recipients and any prepended body, or pass send=false to let the user review.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
toYes
bodyNoOptional message to prepend
sendNoSend immediately (false = save as draft)
transportNoSMTP sends clean MIME and preserves reply threading; requires SMTP configuration. AppleScript uses Mail.app and may quote-wrap the new body on macOS 15+. Omit to prefer configured SMTP when sending; drafts use AppleScript. A selected SMTP transport never silently falls back. SMTP with send=false is rejected.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
okNo
sentNo
messageIdNo
transportNo
recipientsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv2.17.8
    • addedInput schema / properties / transport
      Added value: +{
+  "description": "SMTP sends clean MIME and preserves reply threading; requires SMTP configuration. AppleScript uses Mail.app and may quote-wrap the new body on macOS 15+. Omit to prefer configured SMTP when sending; drafts use AppleScript. A selected SMTP transport never silently falls back. SMTP with send=false is rejected.",
+  "enum": [
+    "applescript",
+    "smtp"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / messageId
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / transport
      Added value: +{
+  "enum": [
+    "smtp",
+    "applescript"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changedv2.10.24
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changedv2.10.8
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
  4. Addedv2.9.0
  5. Removedv2.8.10
  6. First observedv2.6.1

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full behavioral burden. It warns that send=true sends real email immediately, cannot be unsent, and requires explicit user confirmation. It also discloses transport-specific behaviors like AppleScript quote-wrapping and SMTP fallback refusal, going well beyond basic expectations.

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?

The description is front-loaded with the core use case, then alternatives, then safety. Every sentence serves a purpose, and the high-risk send behavior is prominently placed. It is detailed but not bloated.

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 message-forwarding tool with no annotations, the description covers when to use, when not to use, return value, safety behavior, draft behavior, and transport nuances. Given the output schema exists and the description addresses all decision-relevant aspects, nothing critical is missing.

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 60%, and the description adds meaningful semantics for parameters: 'to is an array', 'body to prepend', and 'send=false to save as a draft'. It reinforces the send parameter's safety implication, which the schema alone does not convey. It does not detail the id format, but the schema pattern partially covers that.

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?

The description states a specific verb and resource: forwarding an existing message by id to new recipients, with an optional prepended body. It clearly distinguishes itself from reply-to-message and send-email/create-draft, making the tool's unique role unambiguous.

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?

Explicit 'Use when' and 'Do not use when' sections name the exact conditions and alternative tools. It also provides critical guidance on when to set send=false, which directly informs agent decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sweetrb/apple-mail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server