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

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. 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."
  3. 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."
  4. 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."
  5. 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."
  6. 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"
+}
  7. 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"
  8. First observed

TDQS

A4.5/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 real behavioral detail the annotations cannot express: the confirm gate, the platform boundary, and the blast-radius distinction between deleting one occurrence versus an entire series. It stops short of stating irreversibility or what the deletion returns, which keeps it off a 5.

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, no filler, with the identification and confirm requirement front-loaded before the recurring-event nuance and the sibling pointer. Every clause carries operational weight.

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?

For a destructive single-purpose delete with an output schema, full parameter coverage, and destructive annotations, the description covers platform, confirmation requirement, recurrence scope, and the correct alternative. Nothing an agent needs to invoke it safely 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 coverage is 100% and the span parameter's description already spells out 'this'/'future'/'all'/'series' semantics, so the description is largely restating structured data. It reinforces the default-single-occurrence behavior but adds no syntax or edge-case detail beyond the schema. 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 and resource ("Deletes an event from the Mac's Calendar app (Calendar.app) by ID") and pins the platform, which immediately separates it from the many other delete/event tools. An agent can distinguish it from m365_delete_event and update_calendar_event without opening any 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 preconditions ("Requires confirm=true"), the default behavior, the opt-in variant for recurring events, and an explicit alternative for the Microsoft 365 case ("use m365_delete_event instead"). When-to-use, when-to-use-something-else, and the safety gate are all stated.

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