Skip to main content
Glama
kojott

mailmcp

by kojott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Send a saved draft

send_draft
Destructive

Send a draft exactly as stored in your Drafts folder, including attachments, with recipients taken from the draft and validated against the send allowlist.

Instructions

Sends a draft exactly as stored in the Drafts folder (including its attachments); it leaves Drafts (on Outlook it moves to Sent). Recipients are taken from the draft and must match send_allowlist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesuid of the draft (from create_draft or search_messages in the Drafts folder)
folderNoDrafts folder path if not the default
accountYesAccount id from list_accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.8.1
    • addedInput schema / properties / uid / maxLength
      Added value: +512
    • removedInput schema / properties / uid / maximum
      Removed value: -9007199254740991
    • addedInput schema / properties / uid / minLength
      Added value: +1
    • removedInput schema / properties / uid / minimum
      Removed value: -1
    • changedInput schema / properties / uid / type
      Previous value: -"integer"New value: +"string"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark it destructive, but the description adds meaningful behavior: includes attachments, leaves Drafts, moves to Sent on Outlook, and enforces send_allowlist on recipients. This goes beyond what annotations provide and warns about state-changing effects.

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 concise sentences convey the core action, side effects, attachment behavior, and recipient constraint with no filler. The key distinction is front-loaded before the details.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a send operation with no output schema, the description covers the action, attachments, folder side effects, and recipient authorization constraint. No essential operational detail is missing for an agent to invoke 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 the schema already explains the account, uid, and folder parameters. The description adds operational context about recipients and allowlist, but no additional parameter-specific semantics beyond the schema.

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?

The description uses a specific verb and resource: 'Sends a draft exactly as stored in the Drafts folder', including its attachments, and clarifies the side effect of leaving Drafts/moving to Sent. This clearly distinguishes it from siblings like send_message or create_draft because it is about submitting an existing saved draft unchanged.

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?

It states the precise context: use when sending a saved draft as-is, with recipients taken from the draft and subject to send_allowlist. It does not explicitly name alternative tools or when-not-to-use cases, but the context is clear enough for an agent to select it over send_message or create_draft.

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