Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

reply_message

Sends an immediate reply to a specified Outlook message, preserving thread history automatically.

Instructions

Reply to a Message. Thread history is preserved automatically. The reply is sent immediately.

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_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.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose two meaningful traits: thread history is preserved automatically, and the reply is dispatched immediately (i.e., no draft stage, effectively irreversible). It omits other relevant behavior such as permission/auth requirements, whether the reply lands in the Sent folder, and what happens on an invalid messageId.

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 zero filler, and the statement of purpose is front-loaded ahead of the behavioral notes. Each sentence contributes a distinct fact.

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

Completeness3/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 purpose and the two most consequential behaviors (thread preservation, immediate send). It is still thin on disambiguation from the reply_all/reply_draft siblings and on any return or failure information, which an agent needs to choose and 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 both parameters (messageId, comment) are already documented in the schema and the baseline of 3 applies. The description adds no extra meaning, such as whether messageId accepts a draft ID or a conversation ID, or whether comment supports plain text only.

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?

"Reply to a Message" names a specific verb and resource, so the core action is unambiguous. However, the sibling list contains reply_all_message, reply_draft, and reply_all_draft, and the description never states how this plain reply differs from those variants (e.g., recipients limited to the sender, requires a received message rather than a draft).

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 explicit when-to-use, when-not-to-use, or alternative routing. The agent must infer from the name alone that reply_all_message should be chosen when all recipients must be included, and that reply_draft targets an unsent draft rather than a received message.

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