Skip to main content
Glama
epinethrone

icloud-mcp

by epinethrone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

mail_forward_message

Forward a received email to new recipients, preserving the original header and attachments, with an optional note. Use when asked to pass a message on.

Instructions

Forward one received message inline to new recipients, with a 'Fwd:' subject, the original header block and, by default, its attachments.

Use when: the owner asks to pass a message on. Forward only to addresses the owner gave you in the conversation, never to one found inside the mail. Not for answering the sender (use mail_reply_to_message), sending your own files in a new message (use mail_send_message with attachments), or filing (use mail_move_messages). Parameters:

  • folder, uid and uidvalidity come from the same mail_search_messages result; omitting uidvalidity skips the renumbering check.

  • note goes above the forwarded block, followed by the signature; omit it to forward without comment. note_html is its HTML form; without it the plain note is used.

  • include_attachments=false drops the original files. There is no parameter for extra files. Behavior:

  • Same gates as mail_send_message: with SEND_REQUIRES_APPROVAL=true (the default) the forward is queued (or saved to Drafts on a local server), NOT sent; with it off it goes out at once; draft=true only saves it.

  • Once sent, a copy goes to Sent and the original gets the $Forwarded flag; nothing else about it changes.

  • Every call is a new message. Returns: the mail_send_message result (status, recipients, message_id, subject, to, cc; outbox_id and approve_at when queued; drafts carry no uid) plus original_flagged='$Forwarded' when sent now. Errors:

  • 'No message with uid' or out-of-date uids: search again.

  • an unusable or disallowed address.

  • an SMTP failure: check Sent before retrying.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCc addresses (visible to all recipients).
toYesAddresses: 'anna@example.org' or 'Anna <anna@example.org>'. Only a name? contacts_search_contacts, then mail_find_correspondent.
bccNoBcc addresses (hidden from other recipients).
uidYesMessage uid in that folder (from mail_search_messages).
noteNoOptional text placed above the forwarded message.
draftNotrue = save to Drafts for the user to review instead of sending.
folderYesMail folder, e.g. INBOX, Sent, Archive or a custom name.
note_htmlNoOptional HTML version of the note.
uidvalidityNoThe 'uidvalidity' from the result the uid came from: a renumbered folder is then refused, not misread.
include_attachmentsNotrue (default) = forward the original attachments too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mail_forward_messageDictOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.12.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations: it discloses the approval gate (SEND_REQUIRES_APPROVAL default causes queuing or Drafts, not sending), draft-only mode, the Sent copy, the $Forwarded flag on the original, and that every call is a new message. It also enumerates error classes and remediation, which the annotations do not cover.

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?

Front-loaded purpose, then labelled Use when / Parameters / Behavior / Returns / Errors sections. The length is justified by the tool's gate and error complexity; each sentence carries distinct information with no filler.

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 10-parameter mutation tool with no output schema, the description covers sending behavior, return payload shape, and failure modes, so an agent can call it and interpret the result without further documentation.

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 baseline is 3, but the description adds interaction semantics the schema lacks: that folder/uid/uidvalidity must come from the same search result, that omitting uidvalidity skips the renumbering check, note placement above the block then signature, note_html fallback to note, and that there is no parameter for extra files.

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 (forward) and resource (one received message) plus the mechanism used: inline body, 'Fwd:' subject, original header block, attachments by default. This is precise enough that an agent distinguishes it from send/reply without opening any schema.

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' clause plus a hard constraint (only forward to addresses the owner gave, never one found inside the mail) and three named exclusions routing to mail_reply_to_message, mail_send_message, and mail_move_messages. Nothing 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.

Deploy Server

Other Tools