Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

reply_all_message

Reply to an Outlook message by sending your response to the original sender and all recipients while preserving the email thread automatically.

Instructions

Reply to a Message, sending immediately to the sender and all original Recipients. Thread history is preserved automatically.

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>",
      "comment": "<comment>"
    },
    "name": "reply_all_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesThe reply body text
messageIdYesThe Message ID to reply to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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. It does disclose two useful traits — the reply is sent immediately rather than saved, and thread history is preserved — but says nothing about authentication/account context, whether the reply is stored in Sent, or what happens on failure.

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 with the action and scope front-loaded and the thread-preservation behavior following. Nothing is redundant or padded.

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?

For a two-parameter tool with no output schema, the description covers the essential behavior: it sends rather than drafts, and it targets all original recipients. Remaining gaps around account context and result handling are minor at this complexity level.

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%, with both messageId and comment documented in the schema, so the baseline is 3. The description adds no extra meaning about the ID format, whether the messageId must be from the same thread, or whether the comment supports HTML.

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 description gives a specific verb and resource ("Reply to a Message") and clarifies the recipient scope ("the sender and all original Recipients"), which implicitly separates it from a sender-only reply. It never names the sibling reply_message, so the differentiation has to be inferred from the phrase "all original Recipients."

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?

Usage is only implied: sending to all recipients signals the case where the whole thread should see the reply, and "sending immediately" implies this is not a draft path. There is no explicit when-not guidance and no reference to the draft-based alternatives such as reply_all_draft.

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