Skip to main content
Glama

graph_forward_mail

Forward an Outlook email to one or more recipients, with an optional note, and optionally save it as an unsent draft in your or a shared mailbox.

Instructions

Forward an email to other recipients.

Args: message_id: The email message ID to forward. to: List of recipient email addresses. comment: Optional note to add above the forwarded message. When is_html is true, send explicit HTML; markdown is not converted. is_html: Whether the comment is HTML content (default: True). Use false for plain text. as_draft: Whether to leave the forward as an unsent draft (default false). Returns the created draft instead of a sent status. mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

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

Input Schema

NameRequiredDescriptionDefault
toYes
commentNo
is_htmlNo
mailboxNo
as_draftNo
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that as_draft returns the created draft instead of a sent status, that markdown is not converted when is_html is true, that an empty mailbox targets your own mailbox, and that shared mailboxes need delegated Mail.*.Shared permissions. Remaining gaps are attachment handling on forward, error behavior, and what the non-draft response looks like.

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 line is front-loaded and the remaining content is a tight per-argument list with no filler. The args block duplicates the schema structurally, but since the schema has no descriptions this duplication is load-bearing rather than wasteful.

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 six-parameter mutation tool with no annotations and no output schema, the parameter coverage is solid but the description says nothing about whether original attachments and formatting are preserved, what the sent-status response contains, or what failures look like. Those omissions matter for an agent deciding whether the call achieved its goal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 compensate, and it documents every one of the six parameters — including defaults (is_html true, as_draft false), the sentinel meaning of empty mailbox, and the HTML-vs-markdown conversion caveat. This adds meaning well beyond the bare JSON types.

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?

The first line gives a concrete verb and resource — 'Forward an email to other recipients' — which is immediately distinguishable from siblings like graph_reply_mail or graph_send_mail. It stops short of explicitly contrasting itself with those siblings, so it is clear but not differentiating.

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?

There is no guidance on when to choose forwarding over graph_reply_mail or graph_create_mail_draft, and no prerequisites are stated up front. The as_draft and mailbox parameters hint at usage contexts (draft workflows, shared mailboxes), but that is inference rather than stated guidance.

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