Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Microsoft 365 Delete Event

m365_delete_event
Destructive

Deletes an event from the connected Microsoft 365 / Outlook calendar by its id (from m365_list_events). If the user organizes the meeting and it has attendees, Microsoft 365 sends them a cancellation. For a recurring event the id from m365_list_events is the whole series: deleting it removes every occurrence. Requires confirm=true; without it nothing is deleted. Tell the user which event it is (subject and date) before confirming — the id alone does not say. For the Mac's Calendar app use delete_calendar_event instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEvent ID from m365_list_events
accountNoWhich 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.
confirmYesSet to true to confirm deletion (required)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
accountNoThe email (UPN) of the Microsoft 365 account this call used.
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds real behavioral context beyond them: attendee cancellation emails are sent when the user organizes, a recurring event's id is the whole series so all occurrences are removed, and deletion is blocked without confirm=true. This is exactly the kind of consequence disclosure a delete tool needs.

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?

Front-loaded with the core action, then follow-on behaviors, the confirm gate, and the alternative. Every sentence carries distinct information with no filler.

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 no explanation, and the description covers the destructive semantics, confirmation requirement, id provenance, and the sibling alternative. An agent has everything needed to invoke it safely.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it clarifies that id comes from m365_list_events and, for recurring events, denotes the entire series, and it reinforces that confirm gates the deletion. The account parameter is left to the schema.

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 and resource ('Deletes an event from the connected Microsoft 365 / Outlook calendar by its id') and names the sibling that produces the id (m365_list_events). It is clearly distinguishable from delete_calendar_event, which it explicitly routes away.

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?

Explicit when-to-use (deleting M365/Outlook events by id), when-not (Mac Calendar app → delete_calendar_event), the confirm=true gate, and a procedural safeguard to state subject/date before confirming. 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 toolsInspect
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.

Resources