Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

forward_message

Send an existing Outlook email to one or more new recipients by message ID, optionally adding a prepended comment for context.

Instructions

Forward a Message to one or more new Recipients. Optionally include a comment prepended to the forwarded message.

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_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient email addresses to forward to
commentNoOptional note to prepend to the forwarded message
messageIdYesThe Message ID to forward

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely fails to. It does not say whether the forward is dispatched immediately (an irreversible send-like side effect), whether attachments and original body are carried over, what happens with an invalid recipient, or what the response contains.

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?

Two short sentences, front-loaded with the action and followed by the optional modifier; nothing is padded. The only minor overlap is restating the optional comment, which the schema already flags as optional.

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

Completeness2/5

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

For a three-parameter, send-like tool with no annotations and no output schema, the description is too thin: the agent lacks confirmation that forwarding actually delivers mail and what happens on partial recipient failure. Schema coverage is complete, but the operational consequences of invoking it are undocumented.

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 'to' and 'comment' are already documented; the baseline of 3 applies. The description does add one useful nuance by stating the comment is prepended to the forwarded message, but it adds nothing about recipient format limits or messageId semantics beyond the schema.

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 to one or more new Recipients') plus the optional comment behavior, so the operation is unambiguous. It does not explicitly distinguish itself from nearby siblings such as reply_message or forward_draft, so the agent must infer the boundary from the names alone.

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 when-to-use or when-not-to-use guidance, and no alternatives are named. An agent gets no signal about choosing this over reply_message/reply_all_message (redirecting an existing thread) or forward_draft (working with an unsent draft), nor about prerequisites like the message existing in an accessible folder.

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