Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

send_draft

Sends a previously saved Outlook draft by message ID, enabling you to transmit prepared emails to recipients without recreating them.

Instructions

Send a previously saved Draft by its message ID. Use save_draft to create a Draft, update_draft to edit it, then send_draft to transmit it to Recipients.

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": "send_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYesThe Draft message ID to send

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the key behavioral fact that this transmits to Recipients, i.e. an externally visible, irreversible side effect. It does not say whether the Draft is consumed, moved to a Sent folder, or what happens if the ID is invalid.

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, purpose front-loaded, with the workflow follow-up as the second sentence; nothing redundant.

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 one-parameter, no-output-schema tool this covers purpose, prerequisite state, and sequencing. The only meaningful omission is post-send behavior (draft lifecycle, error on bad ID), a minor gap given the tool's simplicity.

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 coverage is 100% and the single parameter is already described as 'The Draft message ID to send.' The description adds only the qualifier that the ID refers to a Draft rather than an arbitrary message, which is marginal added meaning.

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 ('Send a previously saved Draft by its message ID'), making clear this operates on an existing stored Draft rather than composing a new message, which separates it from send_email and the reply/forward family.

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?

Explicitly places the tool in a workflow: save_draft creates, update_draft edits, send_draft transmits, and it notes the Draft must be 'previously saved.' It gives clear context but no explicit when-not guidance (e.g., use send_email instead for unsaved content).

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