Skip to main content
Glama
owlpost

owlpost

forward_email

Forward a chosen email from an account folder to new recipients, add an optional note, and reattach original attachments. Confirm before sending.

Instructions

Forward a message to new recipients and send it immediately; confirm with the user first.

The subject gets a "Fwd:" prefix, the original headers and plain-text body are included below your note, and the original attachments are re-attached unless include_attachments is false.

Args: account: Account name from list_accounts. folder: Folder containing the message to forward. uid: UID of the message to forward. to: Recipient email addresses. body: Optional note placed above the forwarded content. cc: Cc recipient addresses. bcc: Bcc recipient addresses. attachments: Extra local file paths to attach. include_attachments: Re-attach the original message's attachments (default true).

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": {
      "account": "<account>",
      "folder": "<folder>",
      "uid": "<uid>",
      "to": "<to>"
    },
    "name": "forward_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
uidYes
bodyNo
folderYes
accountYes
attachmentsNo
include_attachmentsNo

Output Schema

NameRequiredDescriptionDefault
ccYes
toYes
bccYes
fromYes
subjectYes
warningNo
message_idYes
size_bytesYes
saved_to_folderYes
refused_recipientsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "bcc": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "Bcc",
      +      "type": "array"
      +    },
      +    "cc": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "Cc",
      +      "type": "array"
      +    },
      +    "from": {
      +      "title": "From",
      +      "type": "string"
      +    },
      +    "message_id": {
      +      "title": "Message Id",
      +      "type": "string"
      +    },
      +    "refused_recipients": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "Refused Recipients",
      +      "type": "array"
      +    },
      +    "saved_to_folder": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "title": "Saved To Folder"
      +    },
      +    "size_bytes": {
      +      "title": "Size Bytes",
      +      "type": "integer"
      +    },
      +    "subject": {
      +      "title": "Subject",
      +      "type": "string"
      +    },
      +    "to": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "To",
      +      "type": "array"
      +    },
      +    "warning": {
      +      "title": "Warning",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "message_id",
      +    "from",
      +    "to",
      +    "cc",
      +    "bcc",
      +    "subject",
      +    "saved_to_folder",
      +    "size_bytes",
      +    "refused_recipients"
      +  ],
      +  "title": "SendResult",
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is partially covered. The description still adds real value beyond them: content transformation ("Fwd:" prefix, original headers and body below the note, attachments re-attached) and the confirm-first requirement. It does not state that repeated calls each produce a new outgoing email, so duplicate-send risk is only implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the confirm-first rule are front-loaded, and the Args block is scannable with no filler. The two paragraphs are dense but every clause (prefix, headers, body placement, attachment default) conveys behavior an agent would otherwise have to guess.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, side effects, the confirm-first safety step, and every parameter for a 9-parameter mutation tool. Only edge behavior (invalid uid, missing attachments, failure modes on an open-world send) is left unstated.

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 description coverage is 0%, so the description must carry the full burden, and its Args block does document all nine parameters, including the non-obvious ones (account from list_accounts, body as a note placed above forwarded content, include_attachments defaulting to true). It adds no format guidance for addresses or uid syntax, so not a full 5.

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 first sentence names a specific verb and resource ("Forward a message") plus the immediate consequence ("send it immediately"), which distinguishes it from send_email, reply_email, and save_draft_email in the sibling list without opening a 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?

It gives a clear usage directive — "confirm with the user first" before an external, irreversible send — and the account/folder/uid framing shows it applies to existing messages. It stops short of explicitly directing the agent away from send_email/reply_email when those are the better fit.

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