Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

reply_draft

Creates a draft response to the original sender for review before sending. Use it to edit or approve the message, then send the saved draft.

Instructions

Create a reply Draft addressed to the original sender, instead of sending 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>"
    },
    "name": "reply_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 burden and does disclose the key trait: nothing is sent, a draft is created for later review, and send_draft finalizes it. It omits where the draft lands (folder), whether a prior draft is superseded, and any auth/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?

Three short sentences with no waste, front-loading the action and the send-vs-draft distinction before the follow-up step. The final sentence supplies return-value information that is needed because no output schema exists.

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 tool with full schema coverage and no output schema, the description covers the action, the non-sending semantics, the next step, and the returned fields. Nothing an agent needs to invoke it correctly is missing.

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 three parameters, including the contentType enum, are already documented. The description adds no extra meaning about how messageId or comment map to the created draft, so the baseline 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?

States a specific verb and resource ("Create a reply Draft") plus a scope qualifier ("addressed to the original sender") that separates it from the reply-all and immediate-send siblings. An agent can tell what this produces without opening the 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?

Gives a clear workflow: create the draft instead of sending, review/edit it, then call send_draft, which is named explicitly. It stops short of stating when to prefer this over reply_message (immediate send) or reply_all_draft, so the alternatives are only implied.

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