Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Delete Calendar Event

delete_calendar_event
Destructive

Deletes an event from the Mac's Calendar app (Calendar.app) by ID. Requires confirm=true. For a repeating event, pass span='future' to delete the whole series (this and all following occurrences); the default deletes only the single occurrence named by event_id. For Microsoft 365 use m365_delete_event instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spanNoFor a recurring event: 'this' (default — only this occurrence) or 'future' (this and all following occurrences; 'all'/'series' mean the same). Any other value is refused. Ignored for non-recurring events.
confirmNoMust be true to delete
event_idYesEvent (or occurrence) identifier from list_calendar_events. For a recurring event this addresses exactly the occurrence that id came from — the preview names the date and scope so you can confirm before deleting.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / event_id / description
      Previous value: -"Event identifier from list_calendar_events"New value: +"Event (or occurrence) identifier from list_calendar_events. For a recurring event this addresses exactly the occurrence that id came from — the preview names the date and scope so you can confirm before deleting."
    • changedInput schema / properties / span / description
      Previous value: -"For a recurring event: 'this' (default — only this occurrence) or 'future' (this and all following occurrences). Ignored for non-recurring events."New value: +"For a recurring event: 'this' (default — only this occurrence) or 'future' (this and all following occurrences; 'all'/'series' mean the same). Any other value is refused. Ignored for non-recurring events."
  2. Changed2 schema fields changed
    • changedInput schema / properties / event_id / description
      Previous value: -"Event (or occurrence) identifier from list_calendar_events. For a recurring event this addresses exactly the occurrence that id came from — the preview names the date and scope so you can confirm before deleting."New value: +"Event identifier from list_calendar_events"
    • changedInput schema / properties / span / description
      Previous value: -"For a recurring event: 'this' (default — only this occurrence) or 'future' (this and all following occurrences; 'all'/'series' mean the same). Any other value is refused. Ignored for non-recurring events."New value: +"For a recurring event: 'this' (default — only this occurrence) or 'future' (this and all following occurrences). Ignored for non-recurring events."
  3. Changed1 schema field changed
    • changedInput schema / properties / span / description
      Previous value: -"For a recurring event: 'this' (default — only this occurrence) or 'future' (this and all following occurrences). Ignored for non-recurring events."New value: +"For a recurring event: 'this' (default — only this occurrence) or 'future' (this and all following occurrences; 'all'/'series' mean the same). Any other value is refused. Ignored for non-recurring events."
  4. Changed1 schema field changed
    • changedInput schema / properties / event_id / description
      Previous value: -"Event identifier from list_calendar_events"New value: +"Event (or occurrence) identifier from list_calendar_events. For a recurring event this addresses exactly the occurrence that id came from — the preview names the date and scope so you can confirm before deleting."
  5. Changed1 schema field changed
    • addedInput schema / properties / span
      Added value: +{
+  "description": "For a recurring event: 'this' (default — only this occurrence) or 'future' (this and all following occurrences). Ignored for non-recurring events.",
+  "type": "string"
+}
  6. Changed1 schema field changed
    • changedInput schema / properties / event_id / description
      Previous value: -"Event identifier from list_events"New value: +"Event identifier from list_calendar_events"
  7. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark destructiveHint=true, and the description adds meaningful destructive detail: deleting a recurring series via span='future', the default single-occurrence behavior, and the requirement to pass confirm=true. This tells the agent exactly what will be destroyed and what safety gate must be satisfied.

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 with no wasted words. The action, requirement, recurring-event nuance, and sibling alternative are all included and front-loaded.

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?

Given the nuanced recurring-event behavior, the description covers the key conditions, prerequisites, and alternative routing. The output schema covers return-value expectations, and the input schema fully documents parameters, leaving no material gap for an agent to call this correctly.

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 value beyond the schema by clarifying the implications of span ('this and all following occurrences'), the source of event_id (from list_calendar_events), and the preview confirmation behavior. Some redundancy with the schema exists, but the extra context is helpful.

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?

The description states a specific verb and resource: 'Deletes an event from the Mac's Calendar app (Calendar.app) by ID.' It also explicitly differentiates from the Microsoft 365 sibling by naming m365_delete_event as the alternative, so an agent can disambiguate without opening schemas.

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?

It gives clear when-to-use guidance: use this for Calendar.app events, and use m365_delete_event instead for Microsoft 365. It also explains the required confirm=true precondition and the correct span values for recurring events versus the single-occurrence default.

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