Skip to main content
Glama

mailroom_forward

Forward an email and its attachments to one or more addresses, such as sending a supplier receipt to an accounting inbox.

Instructions

Forward a message, attachments included, to one or more addresses (for example a supplier receipt to an accounting inbox).

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": "mailroom_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMessage id from mailroom_search (a numeric uid for Gmail/IMAP, a Graph id for Microsoft 365).
toYesWhere to forward it, comma-separated for several.
folderNoFolder: inbox (default), sent, drafts, trash, junk, archive, all, or a folder name.
accountNoWhich connected mailbox to use (its label from mailroom_accounts). Optional when only one is connected or a default is saved in memory.
commentNoOptional note placed above the forwarded message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose two real behavioral facts beyond the schema's field list: attachments are included and delivery fans out to multiple recipients. It says nothing about irreversibility, whether a copy is retained in a sent folder, or permission/account requirements for a write operation.

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?

A single sentence with the action front-loaded, no redundancy, and a concrete example that earns its place by anchoring the abstraction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter mutation tool with no annotations and no output schema, the description covers the what and the example use but omits side effects and result expectations. The fully documented schema compensates for the parameter side, leaving a moderate behavioral gap.

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 id provenance, folder, account, and comment is already documented. The description's only addition is 'one or more addresses', which loosely maps to the comma-separated 'to' field. 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 two distinguishing traits: attachments are carried over and multiple addresses are allowed. It is clearly separable from mailroom_send (compose new) and mailroom_move, though it never names a sibling explicitly.

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 parenthetical example ('a supplier receipt to an accounting inbox') implies the intended use case, and the schema's id field hints that mailroom_search must come first. There is no explicit when-not guidance or statement of prerequisites in the description itself.

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