Skip to main content
Glama

ews_send_message

Sends email via Exchange Web Services (EWS) for Microsoft tenants that block SMTP and Graph API, with a required preview and explicit confirmation before delivery.

Instructions

Send email via Exchange Web Services. Works on Microsoft tenants that block SMTP and Graph API. Before calling, show the user a full preview (To, CC, BCC, subject, rendered body, attachments) and get explicit confirmation.

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>"
    },
    "name": "ews_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCC recipients (optional, max 50)
toYesRecipient email addresses (1..50)
bccNoBCC recipients (optional, max 50)
subjectYesEmail subject
body_htmlNoHTML body. Separate field from `body_text`: pass the HTML itself, never wrapped in pseudo-tags like `<body_html>`; the server rejects them.
body_textNoPlain text body. Separate field from `body_html`: never concatenate the two or wrap content in pseudo-tags like `<body_text>`; the server rejects them.
account_idNoAccount identifier (defaults to `"default"`)default
referencesNoReferences header for threading (optional)
in_reply_toNoIn-Reply-To message ID for threading (optional)

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • changedInput schema / properties / body_html / description
      Previous value: -"HTML body"New value: +"HTML body.\nSeparate field from `body_text`: pass the HTML itself, never wrapped\nin pseudo-tags like `<body_html>`; the server rejects them."
    • changedInput schema / properties / body_text / description
      Previous value: -"Plain text body"New value: +"Plain text body.\nSeparate field from `body_html`: never concatenate the two or wrap\ncontent in pseudo-tags like `<body_text>`; the server rejects them."
  2. First observedv0.4.12

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, openWorldHint=true), the description adds a real operational constraint: the message leaves the system and therefore requires a rendered preview and explicit user sign-off before the call. It does not cover failure behavior, error surfacing, or whether a failed send can be retried safely — relevant given idempotentHint=false.

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 sentences, both load-bearing: the first establishes what and where, the second establishes the required safety workflow. The pre-call requirement is stated up front rather than buried.

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?

With 9 fully documented parameters, complete annotations, and an output schema that removes the need to describe return values, the description covers the essentials for a non-idempotent outbound-send tool. The preview requirement compensates well for the irreversibility; only error/retry behavior is left unaddressed.

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 body_html/body_text pseudo-tag warnings is already documented in the schema. The description only echoes the field list to preview, and even mentions attachments, which is not a parameter of this tool, so it adds little beyond the structured data.

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?

"Send email via Exchange Web Services" names a specific verb and resource, and the follow-up sentence disambiguates it from the smtp_send_message and graph_send_message siblings by stating the exact condition (Microsoft tenants that block SMTP and Graph API) under which this one applies.

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 gives a clear context for use (tenants blocking SMTP/Graph) and a mandatory pre-call procedure: show a full preview and obtain explicit user confirmation. It stops short of explicitly naming a sibling to prefer when SMTP or Graph is available, so the alternative routing is only implied.

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