Skip to main content
Glama

Outlook Draft Reply

outlook_draft_reply

Saves a reply in Outlook Drafts without sending it, so you can review or edit the message before delivery.

Instructions

Save a reply in Drafts. Does not send it.

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": {
      "entry_id": "<entry_id>",
      "body": "<body>"
    },
    "name": "outlook_draft_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
confirmNoMust be true to run this write or destructive tool.
entry_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is already supplied. The description usefully reinforces that the operation only saves a draft and never sends, but it does not mention the confirm=true requirement, permission needs, or what happens if the draft already exists.

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 short sentences with zero waste: the action is front-loaded and the key negative behavior follows immediately. Nothing is superfluous.

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?

An output schema exists, so return values need not be explained. But for a three-parameter write tool, the description omits the confirm-gating behavior and any discussion of entry_id semantics, leaving some gaps relative to the tool's complexity.

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 33%, with the confirm parameter already documented in the schema as required for write tools. The description adds no parameter-level detail about entry_id or body, though the behavior of these is largely inferable from naming.

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 uses a specific verb and resource: 'Save a reply in Drafts,' and explicitly clarifies that it does not send the message. This distinguishes it from a send action, though it does not name a sibling such as outlook_send_mail.

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 implied by 'Save a reply in Drafts' and the negative statement 'Does not send it,' which tells the agent this is a non-sending path. However, there is no explicit when-to-use versus alternatives guidance, and no mention of prerequisites such as requiring the confirm flag.

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