Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete-specific-calendar-event

delete-specific-calendar-event
Destructive

Delete a specific calendar event from Microsoft 365 by providing its calendar and event IDs. For recurring events, delete the entire series or a single occurrence using the appropriate ID.

Instructions

Delete a specific calendar event. Requires calendarId (the target calendar's ID) and eventId (the event's own ID).

šŸ’” TIP: Deleting a seriesMaster deletes ALL occurrences. To cancel a single occurrence, use the specific instance ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoFor destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: "confirmation_required" } without touching user data.
eventIdYesValue for the 'eventId' path segment. Pass it under the name 'eventId', not as 'id'. Use the 'id' field of the event object as returned by Microsoft Graph.
If-MatchNoETag
calendarIdYesValue for the 'calendarId' path segment. Pass it under the name 'calendarId', not as 'id'. Use the 'id' field of the calendar object as returned by Microsoft Graph.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.134.4
  2. Removedv0.131.2
  3. Changed1 schema field changedv0.131.1
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "For destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: \"confirmation_required\" } without touching user data.",
+  "type": "boolean"
+}
  4. Addedv0.114.0
  5. Removedv0.112.2
  6. Addedv0.110.0
  7. Removedv0.108.0
  8. First observedv0.31.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral detail the annotations cannot convey: that deleting a seriesMaster cascades to ALL occurrences, which materially affects the agent's choice of ID. It does not mention the confirm gate, but the schema parameter documents that fully.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then required params, then a clearly marked TIP. Two compact sentences plus one line of guidance, with minimal waste; the only slight redundancy is restating the two required IDs that the schema already names.

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 destructive 6-parameter operation with no output schema, the description covers the action, the required identifiers, and the highest-risk behavioral trap (occurrence cascade). Annotations carry the safety signal and the schema carries the confirm gate, so nothing critical 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 calendarId, eventId, confirm, If-Match, includeHeaders and excludeResponse are all self-documenting. The description names calendarId and eventId but adds no format, syntax, or constraint detail beyond what the schema already states, so baseline 3 applies.

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?

States a specific verb and resource ('Delete a specific calendar event') so the agent knows the operation immediately. However, the sibling set contains both 'delete-calendar-event' and 'delete-specific-calendar-event', and the description does nothing to explain how this tool differs from that near-identical sibling.

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?

The TIP gives real conditional guidance: deleting a seriesMaster wipes all occurrences, so use a specific instance ID to cancel just one. That is genuinely actionable routing advice. It still does not say when to prefer this over 'delete-calendar-event' or 'cancel-calendar-event', so it stops short of full when/when-not coverage.

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

Deploy Server

Other Tools