Skip to main content
Glama

Create draft

create_draft

Save a new email as a draft in Microsoft 365 without sending it, returning a draft ID for later updates, attachments, or sending.

Instructions

Save a new email in Drafts without sending it. Returns the draft ID for update_draft, add_attachment and send_draft.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCc recipients: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
toNoRecipients: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
bccNoBcc recipients: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
bodyNoMessage body
subjectNoSubject line
bodyFormatNoBody format: "text" (default) or "html"
importanceNoMessage importance
attachmentsNoFiles to attach

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two useful facts beyond that: the draft is not sent, and a draft ID is returned for chaining. It says nothing about validation failures, required fields, or what happens with zero recipients, which matters for a tool with no required parameters.

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, zero waste, with the non-sending constraint and the return value both front-loaded. Nothing could be removed without losing information.

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 an 8-parameter creation tool with no output schema, the description covers the essential behavior and the return value that enables chaining. It is slightly thin on the fact that all parameters are optional and what a minimal valid draft looks like, but the rich schema compensates.

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 every parameter including the nested attachment object is already documented in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 ("Save a new email in Drafts") and immediately distinguishes it from the sending path with "without sending it." An agent can tell this apart from send_draft without opening either schema.

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?

The phrase "without sending it" makes the use case clear, and the description names the follow-up tools (update_draft, add_attachment, send_draft) that consume the returned ID. It stops short of an explicit when-not or prerequisite statement, so it is clear context rather than full routing guidance.

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