Skip to main content
Glama

Send draft

send_draft

Sends an existing Outlook draft, including reply or forward drafts, by draft ID so you can finalize and deliver prepared messages from Microsoft 365 mail.

Instructions

Send an existing draft (including reply/forward drafts).

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": {
      "id": "<id>"
    },
    "name": "send_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDraft ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the write/external-facing nature is known. The description adds only the note that reply/forward drafts are included; it says nothing about irreversibility of delivery, what happens to the draft after sending, or 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?

One short sentence, front-loaded with the action and resource, with no redundant or filler wording. The parenthetical adds genuinely distinct scope information rather than padding.

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 one-parameter send tool with annotations covering the safety profile and no output schema, the description is minimally sufficient. However, it omits post-send behavior (whether the draft is removed from the Drafts folder) and the distinction from send_message, which an agent would want before choosing it.

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?

There is a single parameter (id) with 100% schema description coverage, so the schema already defines the draft ID. The description adds no format, sourcing, or lookup guidance (e.g., where to obtain the ID), so this sits at the adequate baseline.

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?

States a specific verb (send) and resource (an existing draft), and clarifies scope by noting reply/forward drafts are covered. It does not distinguish itself from the sibling send_message, which likely creates-and-sends a new message, so the boundary is left to inference.

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?

The phrase 'existing draft' implicitly tells the agent a draft must already exist (created via create_draft), which is useful implied guidance. There is no explicit when-to-use versus send_message, and no statement of prerequisites such as the draft not already having been sent.

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