Skip to main content
Glama
Sign In
Chronary

Chronary

Official
by Chronary
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_event

Idempotent

Reschedule or edit an event's title, description, start/end times, location, status, reminders, or metadata. Provide only the fields you want to change.

Instructions

Reschedule or edit an event — change its title, description, start/end times, location, status, reminders, or metadata. Use this to move an appointment to a new time or update its details. Provide only the fields you want to change. Holds cannot be edited via this tool (use confirm_event / release_event). External iCal events are read-only. calendar_id is optional — if omitted it is resolved from the event.

Input Schema

NameRequiredDescriptionDefault
titleNoNew event title
statusNoNew event status
all_dayNoWhether this is an all-day event
end_timeNoNew end time (ISO 8601)
event_idYesEvent ID to update
metadataNoReplacement metadata object
remindersNoReminder offsets in minutes before start_time. Omit to leave unchanged, null to inherit the calendar default, [] for no reminders.
start_timeNoNew start time (ISO 8601)
calendar_idNoCalendar ID that owns the event. Optional — if omitted the calendar is resolved from the event.
descriptionNoNew description, or null to clear it
recurrence_ruleNoSet/change the recurring series rule (RFC 5545 RRULE subset, full-series semantics), or null to make the event a one-off. Changing the rule or start_time resets cancelled occurrences.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.3
    • removedInput schema / properties / description / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / description / type
      Added value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / end_time / 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))$"
    • changedInput schema / properties / start_time / 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 / recurrence_rule
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 256,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Set/change the recurring series rule (RFC 5545 RRULE subset, full-series semantics), or null to make the event a one-off. Changing the rule or start_time resets cancelled occurrences."
+}
  3. First observedv1.2.5

TDQS

A4.2/5.0
Behavior4/5

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

With annotations covering safety (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description adds meaningful behavioral context: partial update semantics ('Provide only the fields you want to change'), a restriction on holds, and read-only behavior for external iCal events. It does not describe the return value or any notification side effects, so it is strong but not exhaustive.

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?

The description is front-loaded with the core purpose, followed by usage guidance and key constraints. Every sentence earns its place: purpose, when to use, partial-update instruction, and two important exclusions. No filler or repetition.

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?

Given 11 parameters, full schema coverage, and annotations covering safety, the description is nearly complete: it covers purpose, usage, partial-update behavior, and key restrictions. It could still mention what a successful update returns or that the operation is idempotent, but the annotations already convey idempotency, making the remaining gap minor.

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 the schema already documents all 11 parameters thoroughly. The description only adds the general partial-update instruction and notes that calendar_id is optional and resolved from the event, which largely duplicates the schema's own description for calendar_id. Baseline 3 is appropriate when the schema does the heavy lifting.

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: 'Reschedule or edit an event — change its title, description, start/end times, location, status, reminders, or metadata.' It also distinguishes from siblings by noting that holds cannot be edited here and must use confirm_event or release_event, and that external iCal events are read-only.

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?

It gives clear context ('Use this to move an appointment to a new time or update its details') and explicit exclusions for holds and external iCal events. However, it does not address when to use this tool versus cancel_event or delete_event, nor does it clarify whether setting status to 'cancelled' is preferred over the cancel_event sibling.

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