Skip to main content
Glama

create_draft

Create an Outlook email draft without sending it. Set recipients, subject, body, and CC; the draft is stored in the Drafts folder for later review and sending.

Instructions

メールの下書きを作る。送信はしない。

このサーバに送信手段は無い。下書きは Outlook の「下書き」フォルダに 置かれるだけで、利用者が自分で開いて送信するまでどこへも出ない。 「送っておいて」と頼まれても、できるのはここまでだと伝えること。

Args: to: 宛先アドレス。カンマ区切りで複数可。 subject: 件名。 body: 本文(平文)。 cc: Cc のアドレス。カンマ区切りで複数可。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNo
toYes
bodyYes
subjectYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations only indicate readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds crucial behavioral context: there is no sending mechanism on this server, drafts are placed in Outlook's Drafts folder, and they remain there until the user sends them. It also instructs the agent to communicate this limitation to users, which is valuable beyond the annotations.

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 description is well-structured and front-loaded: the bold '**送信はしない**' immediately signals the most important caveat, followed by a concise explanation and a clean Args list. Every sentence adds value, and the formatting improves readability.

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 draft-creation tool, the description covers the essential behavioral constraint (no sending), the destination folder, the user-facing instruction, and all parameter semantics. An output schema exists, so the lack of explicit return-value documentation is acceptable. The description is wholly sufficient for an agent to use the tool correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates by explaining each parameter: 'to' and 'cc' accept comma-separated addresses, 'subject' is the subject line, and 'body' is plain text. This adds meaning beyond the bare schema titles and clearly conveys the expected input format.

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?

The description clearly states 'メールの下書きを作る' (create an email draft) and emphasizes '**送信はしない**' (does not send), giving a specific verb and resource. However, it does not explicitly distinguish this from the sibling tool 'draft_reply', which likely creates a reply draft, leaving some ambiguity about whether this is for new emails only.

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 description explicitly states when not to use it (when sending is requested) and instructs the agent to tell the user that only draft creation is possible. It provides clear context for the tool's scope but does not name alternatives like 'draft_reply' for reply-draft scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ma2no4413/outlook-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server