Skip to main content
Glama
marius-cetanas

macos-mail-mcp

by marius-cetanas
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

forward_message

Forward an existing email to a new recipient by specifying the message, mailbox, and target address. Optionally prepend text to the forwarded body.

Instructions

Forward an existing email message to a new recipient. Returns the sender the forward was sent from. Does not support adding new attachments (Mail.app limitation).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesThe recipient email address to forward to
bodyNoOptional text to prepend to the forwarded message body
messageIdYesThe numeric ID of the message to forward
accountNameYesThe name of the account containing the mailbox. This locates the source message only — it does not control which account sends. Use fromAccount for that.
fromAccountNoAccount to send from — a Mail account name ("Google") or one of its addresses ("you@gmail.com"), as reported by list_accounts. Matching is case-insensitive and an unrecognised value is an error, never a silent fallback. Omit to use Mail's default sending account; either way the account used is returned as `sender`.
mailboxNameYesThe name of the mailbox containing the message

Schema Changelog

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

  1. Changed5 schema fields changedv1.3.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / accountName / description
      Previous value: -"The name of the account containing the mailbox"New value: +"The name of the account containing the mailbox. This locates the source message only — it does not control which account sends. Use fromAccount for that."
    • addedInput schema / properties / fromAccount
      Added value: +{
+  "description": "Account to send from — a Mail account name (\"Google\") or one of its addresses (\"you@gmail.com\"), as reported by list_accounts. Matching is case-insensitive and an unrecognised value is an error, never a silent fallback. Omit to use Mail's default sending account; either way the account used is returned as `sender`.",
+  "type": "string"
+}
    • addedInput schema / properties / messageId / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / messageId / minimum
      Added value: +-9007199254740991
  2. First observedv1.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does meaningful work: it discloses that the tool returns the sender account, and it flags an important behavioral limitation (no new attachments due to Mail.app). It could add more about side effects or failure modes, but the core behavior is transparent.

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 three concise sentences. The main action is front-loaded, the return value is specified, and the limitation is stated directly with no unnecessary filler.

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?

Given the schema already covers all parameter semantics, the description is nearly complete: it explains the action, the return value, and the attachment limitation. The only missing piece is explicit routing guidance among the related sibling tools.

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?

All parameters have complete descriptions in the schema, so the description does not need to compensate. It adds useful behavioral context around the sender and attachment limitation, but it does not provide additional parameter-specific details beyond what the schema already contains.

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: forward an existing email message to a new recipient. This clearly distinguishes it from siblings like send_message and reply_to_message because it explicitly describes forwarding an existing message rather than composing a new one or replying to the original sender.

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?

The usage is implied by the purpose: use this when a user wants to forward an existing message to a new recipient. However, the description does not explicitly mention when not to use it or name alternatives like send_message for new emails or reply_to_message for replying to the sender.

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/marius-cetanas/macos-mail-mcp'

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