Local MCP

Microsoft 365 Send Email

m365_send_email

Use this when the user wants to send from their Microsoft 365 / Outlook account via the cloud — requires a connected M365 account. Shows a preview first — set confirm=true to actually send. For sending from an account configured in the Mac's Mail.app, use send_email.

Input Schema

TableJSON Schema

Name	Required	Description
`cc`	No	CC recipients (optional, comma-separated)
`to`	Yes	Recipient email address. For multiple, separate with commas.
`body`	Yes	Email body (plain text)
`account`	No	Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.
`confirm`	No	Set to true to actually send (default: shows preview only)
`subject`	Yes	Email subject

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No
`account`	No	The email (UPN) of the Microsoft 365 account this call used.
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 5, 2026

addedInput schema / properties / account

Added value: +{
+  "description": "Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.",
+  "type": "string"
+}

addedOutput schema / properties / account

Added value: +{
+  "description": "The email (UPN) of the Microsoft 365 account this call used.",
+  "type": "string"
+}

First observedJun 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety/target profile is already given. The description adds meaningful context beyond that: preview-by-default and the confirm=true requirement to actually dispatch. It does not cover rate limits or failure modes, but for an email send this is solid disclosure.

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?

Three sentences, zero waste, and the key routing information (M365 vs Mail.app) plus the send gate are front-loaded. Every sentence earns its place.

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?

An output schema exists, so return values need not be explained. For a six-parameter mutation tool with full schema coverage and annotations, the description covers the account prerequisite, the preview/confirm behavior, and the sibling alternative – nothing an agent needs to call it correctly is missing.

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 all six parameters (including confirm and account) are already documented in the schema; baseline is 3. The description reinforces confirm and the connected-account requirement but adds no syntax or format detail beyond what the schema provides.

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 (send) and resource (email) with explicit scope: sending from the user's Microsoft 365 / Outlook account via the cloud. It also names the sibling it is not (send_email for Mac Mail.app), so an agent can distinguish the two 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 Guidelines5/5

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

Gives explicit when-to-use ('user wants to send from their Microsoft 365 / Outlook account'), a prerequisite ('requires a connected M365 account'), and a named alternative for the other case ('For sending from an account configured in the Mac's Mail.app, use send_email'). It also documents the preview-first flow and the confirm=true gate to actually send.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.