Local MCP

Microsoft 365 Reply Email

m365_reply_email

Destructive

Use this when the user wants to reply to a Microsoft 365 email (message ID from m365_list_emails). Requires a connected M365 account. Shows a preview first — set confirm=true to actually send. For replying to a message found in Apple Mail, use reply_email.

Input Schema

Name	Required	Description
`id`	Yes	Message ID to reply to (from m365_list_emails or m365_read_email)
`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)
`message`	Yes	Your reply text, as plain text. Line breaks and blank lines are kept.
`remember`	No	With confirm: true, also stop asking for this kind of action from now on. Only when the person said so ("don't ask again"). The person can revoke it in LMCP or with set_always_allowed.
`reply_all`	No	If true, reply to all recipients (default: false)

Output 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.

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / remember

Added value: +{
+  "description": "With confirm: true, also stop asking for this kind of action from now on. Only when the person said so (\"don't ask again\"). The person can revoke it in LMCP or with set_always_allowed.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / message / description

Previous value: -"Your reply text"New value: +"Your reply text, as plain text. Line breaks and blank lines are kept."

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.4/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and openWorldHint=true, but the description adds the key behavioral fact those don't convey: it shows a preview first and only sends with confirm=true. It also states the connected-account requirement. It stops short of describing the preview contents or send side effects, but the safety-critical flow is disclosed.

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 tight sentences: purpose first, then prerequisite, then the confirm/preview contract, then the sibling fallback. No filler, and the highest-value routing cue (reply_email for Apple Mail) is included without bloat.

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?

For a 6-param mutating tool with an output schema, the description covers the account requirement, the id provenance, and the preview/send gate. Return values are handled by the output schema, so the remaining gap (preview payload detail, rate limits) is minor.

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 confirm, remember, and reply_all is already documented in the schema. The description only reinforces the confirm preview behavior and the source of the id, adding little beyond structured fields; baseline 3 applies.

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+resource ('reply to a Microsoft 365 email') and anchors the id to m365_list_emails. It also explicitly carves itself out from the generic reply_email sibling, so the agent can disambiguate 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 reply to a Microsoft 365 email'), a prerequisite (connected M365 account), and a named alternative for the adjacent case ('For replying to a message found in Apple Mail, use reply_email'). Nothing is left to inference.

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.