Skip to main content
Glama

Forward email

forward_message

Forwards an email message and its attachments to new recipients, sending immediately unless you choose to save it as a draft.

Instructions

Forward a message (with its attachments) to new recipients. Sends immediately unless send is false.

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 recipients: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
idYesID of the message to forward
toYesRecipients: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
bccNoBcc recipients: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
bodyNoText to add above the forwarded message
sendNoSend now (default true) or save as draft (false)
bodyFormatNoBody format: "text" (default) or "html"
attachmentsNoFiles to attach

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context that the send happens immediately unless send is false, and that attachments carry over. It does not mention permission requirements or what happens to the original message, so it is a modest addition rather than rich disclosure.

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 short sentences with zero waste; the core action is front-loaded and the send-timing caveat follows immediately. Nothing is redundant or padded.

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?

For an 8-parameter mutation tool with full schema coverage and no output schema, the description covers the essential action and the immediate-send side effect. It could say more about draft behavior or recipient validation, but an agent has enough to call it correctly.

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 including send, bodyFormat and the attachment object is already documented. The description only echoes the send=false draft behavior and the attachment carry-over, adding little beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ("Forward a message") plus scope ("with its attachments") and target ("new recipients"). It is clearly distinguishable from reply_message and send_message by the verb alone, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance relative to alternatives such as reply_message or send_message, and no prerequisites. The only conditional mentioned ("unless send is false") is a behavioral detail, not a selection rule.

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