Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

reply_all_draft

Creates a reply-all draft addressed to the sender and all original recipients for review before sending. Returns the draft ID, subject, and to/cc fields.

Instructions

Create a reply-all Draft addressed to the sender and all original Recipients, instead of sending immediately. Review who it's going to, 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>"
    },
    "name": "reply_all_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoOptional reply body text
messageIdYesThe Message ID to reply to
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.3/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does it well: mutation is a draft creation, not a send; the recipient set is enumerated as sender plus all original recipients; and the return fields (id, subject, to/cc) are stated. It stops short of permissions, whether original cc is preserved verbatim, or what happens on duplicate drafts.

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 sentences, front-loaded with the create action and recipient scope, followed by the review-then-send workflow and return shape. No filler and nothing buried.

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

Completeness5/5

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

For a three-parameter draft-creation tool with no annotations or output schema, the description covers what is created, who receives it, that nothing is sent, what comes back, and the next step. An agent has everything needed to call it correctly.

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 the schema already explains messageId, comment, and the text/html contentType escape-vs-passthrough behavior. The description adds no parameter-level detail of its own, so it sits at the baseline.

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?

States a specific verb and resource ('Create a reply-all Draft') plus a precise recipient scope (sender and all original Recipients). That wording separates it from reply_all_message (sends) and reply_draft (single-recipient reply) without needing the sibling schemas.

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?

The phrase 'instead of sending immediately' tells the agent this is the non-sending path, and 'Review who it's going to, then use send_draft' gives the follow-up step explicitly. It never names reply_all_message as the immediate-send alternative, so routing is implied rather than stated outright.

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