Skip to main content
Glama

graph_send_mail_draft

Sends an existing draft email by message ID, optionally from a shared mailbox, to complete and deliver prepared messages.

Instructions

Send an existing draft message.

Args: message_id: The draft message ID (from graph_create_mail_draft). mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

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": {
      "message_id": "<message_id>"
    },
    "name": "graph_send_mail_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxNo
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.7/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 add valuable auth context ('Requires the delegated Mail.*.Shared permissions'), which tells the agent a shared-mailbox action may fail without proper consent. However, it omits the key behavioral traits of a send operation: that the message leaves the Drafts folder, that sending is irreversible, and where the sent copy lands.

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?

The core action is front-loaded in a single sentence, followed by tightly scoped per-parameter notes. No sentence is redundant or padding, and the docstring 'Args:' structure makes scanning easy for an agent parsing parameters.

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 two-parameter mutation tool with no annotations and no output schema, the definition covers both parameters, the prerequisite tool, and the permission requirement. What is missing is post-send behavior (draft removal, Sent Items placement) and failure modes, which an agent sending mail would benefit from knowing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it largely does: message_id is explained as the draft ID with its source tool, and mailbox is explained as shared mailbox address or user ID with the empty-string default behavior ('Empty targets your own mailbox') and its permission requirement. It falls short only on accepted formats for mailbox.

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 and resource: 'Send an existing draft message.' The qualifier 'existing draft' distinguishes it from graph_send_mail (new message) and ties it to graph_create_mail_draft, though the description never explicitly names the sibling it is not.

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 rather than stated: the parenthetical '(from graph_create_mail_draft)' establishes the workflow prerequisite, so an agent knows a draft must exist first. There is no explicit when-to-use versus graph_send_mail or a stated exclusion, and no note on what happens if the draft ID is invalid or already sent.

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

Deploy Server

Other Tools