Skip to main content
Glama
Sign In
Chronary

Chronary

Official
by Chronary
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cancel_event

DestructiveIdempotent

Delete or cancel a calendar event, excluding it from future availability; for recurring events, cancel a single occurrence or the whole series.

Instructions

Delete or cancel an event from a calendar. Use this to remove, cancel, or delete any scheduled event or appointment. The event is marked cancelled and excluded from future availability calculations. For a recurring series, pass occurrence_start to cancel just that one occurrence (the series continues); omit it to cancel the whole series. calendar_id is optional — if omitted the calendar is looked up from the event. Provide calendar_id to fail fast on cross-calendar typos.

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent ID to cancel
calendar_idNoCalendar ID that owns the event. Optional — if omitted the calendar is resolved from the event. Matches the asymmetry with confirm_event / release_event which never required this arg.
occurrence_startNoFor recurring events only: ISO 8601 start of the single occurrence to cancel. The rest of the series is unaffected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.3
    • changedInput schema / properties / occurrence_start / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
  2. Changed1 schema field changedv1.4.1
    • addedInput schema / properties / occurrence_start
      Added value: +{
+  "description": "For recurring events only: ISO 8601 start of the single occurrence to cancel. The rest of the series is unaffected.",
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+  "type": "string"
+}
  3. First observedv1.2.5

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds real behavioral substance beyond them: the event is marked cancelled (a soft cancel) and excluded from future availability calculations, and recurring-series cancellation is scoped by occurrence_start. It also explains the optional calendar_id as a fail-fast guard against cross-calendar typos, which is useful operational context.

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?

Four sentences, each carrying distinct information (purpose, post-condition, recurring scope, optional param rationale), and the core purpose is front-loaded. Slight redundancy in the 'remove, cancel, or delete' triple, but nothing is wasted.

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?

With no output schema, the description adequately covers side effects (marked cancelled, removed from availability), the recurring variant, and the optional-parameter tradeoff. It does not address downstream effects such as attendee notifications or whether confirmed events can be cancelled, which is a minor gap.

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 the omit-case semantics for occurrence_start ('omit it to cancel the whole series') that the schema only implies, plus the resolution behavior and rationale for calendar_id. This meaningfully supplements rather than repeats the schema.

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 (delete/cancel) and resource (calendar event) and immediately gives alias terms so an agent can map varied user phrasing onto it. It does not explicitly differentiate itself from related lifecycle siblings like confirm_event or release_event, but no sibling overlaps the cancel/delete semantics, so the purpose is unambiguous.

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?

Gives clear usage context ('remove, cancel, or delete any scheduled event or appointment') and an explicit decision rule for the recurring case: pass occurrence_start to cancel one occurrence, omit it to cancel the series. It stops short of when-not-to-use or naming alternatives, so it is strong but not exhaustive.

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