Skip to main content
Glama

Forward Email

send_forward
Destructive

Forward an email to new recipients and send it immediately, including a quoted copy of the original. Add an optional note for context before delivery.

Instructions

Forward an email to new recipients and send immediately. Quotes the original. Use create_forward_draft to review before sending.

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": {
      "message_id": "<message_id>",
      "to": "<to>"
    },
    "name": "send_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient email address(es), comma-separated for multiple
commentNoOptional note added above the quoted original
mailboxNoEmail address of another mailbox to act on (delegated or shared), e.g. 'someone@example.com'. Omit for your own mailbox; required when this server signs in as an application. Only addresses this server is configured to allow will be accepted.
message_idYesThe message ID to forward

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description adds the key operational fact that the message is sent immediately and quotes the original, which explains why the draft path exists. It does not elaborate on delivery irreversibility or mailbox-delegation permission behavior beyond what the schema states.

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?

Three short sentences, front-loaded with the action and the send-immediately behavior, with the alternative routing last. No redundant restatement of the title.

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 a four-parameter mutation tool with no output schema, the description plus annotations plus fully documented schema cover what an agent needs to invoke it correctly. Minor gap: nothing about delivery side effects on the original message or failure modes.

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 recipients, comment, mailbox, and message_id are all documented in the schema. The description's only added meaning is that the original is quoted, which loosely relates to the comment parameter but adds no syntax or constraint detail. Baseline 3 applies.

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 and resource ('Forward an email to new recipients') plus the immediate-send scope, which is exactly what distinguishes it from create_forward_draft. An agent can tell the two apart without opening either schema.

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?

Names the alternative explicitly ('Use create_forward_draft to review before sending') and gives the condition that selects it, so the review-then-send tradeoff is clear. It stops short of stating when not to use it (e.g. reply vs. forward) or any prerequisite conditions.

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