Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

send_email

Send an email immediately via Microsoft Outlook with To, CC, and BCC recipients, plain text or HTML body, and file attachments up to 3 MB each.

Instructions

Send an email immediately via Microsoft Outlook. Supports To, CC, BCC, plain text or HTML body, and file attachments (max 3 MB each).

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": {
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCC email addresses
toYesRecipient email addresses (required)
bccNoBCC email addresses
bodyYesEmail body content (required)
subjectYesEmail subject (required)
attachmentsNoLocal file paths to attach (max 3 MB per file)
contentTypeNoBody content type: 'text' for plain text, 'html' for HTML (default: 'text')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must disclose side effects. It usefully says the email is sent immediately and caps attachments at 3 MB each, but omits authentication requirements, irreversibility/external delivery implications, and what the tool returns on success or failure.

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 front-loaded sentences: action first, supported capabilities second. No wasted wording, and the key operational limit is included compactly.

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

Completeness3/5

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

For a straightforward 7-parameter send tool with full schema coverage, the definition is sufficient to invoke correctly. But because there are no annotations and no output schema, the missing auth, delivery-result, and failure behavior leave the operational picture incomplete.

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 documents every parameter including the text/html enum and 3 MB attachment limit. The description's parameter list adds little beyond the structured schema, fitting the baseline.

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?

Names a specific verb and resource ('Send an email') plus platform ('Microsoft Outlook') and immediacy, making the core action clear. It does not explicitly contrast with draft-related siblings such as send_draft, so the boundary is implicit rather than stated.

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?

The word 'immediately' implies this is for direct sending rather than saving a draft, but the description gives no explicit when-to-use/when-not-to-use guidance or named alternatives. That leaves an agent to infer the draft-vs-send decision.

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