Skip to main content
Glama
Sign In
Outlook Email MCP Server

Outlook Email MCP Server

by nhatho0001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_draft

Compose a new draft email in your Outlook Drafts folder by specifying recipients, subject, body, and importance.

Instructions

Tạo email nháp mới trong folder Drafts.

Args: to: Địa chỉ email người nhận (nhiều địa chỉ cách nhau bằng dấu phẩy). cc: Địa chỉ CC (tùy chọn). bcc: Địa chỉ BCC (tùy chọn). subject: Tiêu đề email. body: Nội dung email (hỗ trợ plain text hoặc HTML). importance: Độ ưu tiên: low, normal, hoặc high.

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
ccNo
toNo
bccNo
bodyNo
subjectNo
importanceNonormal

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It correctly states the action (create draft) but does not disclose potential side effects, such as whether the draft is automatically saved or if it replaces an existing draft. It does note that body supports plain text or HTML, which adds some transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and uses a clear bulleted Args format. It front-loads the purpose statement. However, it could be slightly shorter by omitting redundancies (e.g., 'Args:' is clear from context).

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?

Given the tool has 6 optional parameters and an output schema, the description adequately covers all parameters' usage. It does not mention prerequisites like authentication, but that is implied by sibling auth tools. The description is sufficient for an agent to invoke the tool correctly.

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?

With 0% schema description coverage, the description adds significant value by explaining each parameter's meaning and constraints. For example, it specifies that 'to' accepts multiple addresses separated by commas, and that 'importance' accepts low, normal, or high. This compensates well for the missing schema descriptions.

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 clearly states the tool creates a new draft email in the Drafts folder, using specific verb 'Tạo' (create) and resource 'email nháp mới' (new draft email). This distinguishes it from siblings like update_draft, send_draft, and list_drafts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool versus alternatives. It does not mention that after creating a draft, one should use send_draft to send it, nor does it specify when not to use it (e.g., for updating existing drafts).

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