Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

forward_draft

Creates a draft to forward a message to new recipients so you can review or edit it before sending, instead of forwarding immediately. Returns the draft's id, subject, and to/cc.

Instructions

Create a forward Draft to new Recipients, instead of forwarding immediately. Review or edit it, then use send_draft. Returns the created Draft's id, subject, and to/cc.

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": {
      "messageId": "<messageId>",
      "to": "<to>"
    },
    "name": "forward_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCC email addresses
toYesRecipient email addresses to forward to (required)
bccNoBCC email addresses
commentNoOptional note to prepend to the forwarded message
messageIdYesThe Message ID to forward
contentTypeNoHow to treat the comment: 'text' (default) HTML-escapes it so it renders literally; 'html' passes it through as-is (validated for unsupported CSS).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full load: it discloses that nothing is sent yet and names the return fields (id, subject, to/cc), which is genuinely useful. It does not cover where the draft is stored, whether the original message body/attachments are included, or any permission requirements.

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 tight sentences: the action and its non-immediate nature first, then the workflow, then the return values. Nothing is redundant and nothing needed is buried.

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?

There is no output schema, but the description compensates by naming the returned fields, and it covers the draft-then-send workflow. For a 6-parameter mutation tool with no annotations, it could still say more about draft persistence and permissions.

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 all six parameters including the contentType enum are already documented in the schema. The description adds no further meaning about required vs optional fields or recipient list behavior, so the baseline of 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?

The description gives a specific verb and resource ("Create a forward Draft") plus a scope qualifier ("to new Recipients") and explicitly contrasts it with immediate forwarding and points to send_draft. An agent can distinguish it from forward_message and send_draft without opening any 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 states the core when-to-use condition ("instead of forwarding immediately") and the follow-up path ("review or edit it, then use send_draft"). The only gap is that it never names forward_message as the tool for the immediate case, leaving that alternative to inference from phrasing.

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