Skip to main content
Glama

Update Calendar Event

update_calendar_event
DestructiveIdempotent

Edit the title, times, or description of a calendar event you created. Omitted fields stay unchanged, and a preview confirmation prevents unintended changes.

Instructions

Change the title, times or description of a calendar event you created. Only events you own can be changed; course events return a permission error. Fields you omit stay the same. [NEEDS CONFIRMATION: call it once for a preview and a confirm_token, show the preview to the user, and only if they say yes call it again with the same arguments, confirm=true and that confirm_token. Apps that can ask the user directly show a confirmation instead.]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "update_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNew title. Omit to keep the current one.
end_atNoEnd time, ISO 8601, e.g. "2026-11-05T15:00:00-05:00".
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
event_idYesCalendar event ID (numeric string). Get it from list_calendar_events or list_my_reservations.
start_atNoStart time, ISO 8601, e.g. "2026-11-05T14:00:00-05:00".
descriptionNoOptional description text.
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / confirm
      Added value: +{
      +  "description": "Set to true together with confirm_token to carry out a request you already previewed.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / confirm_token
      Added value: +{
      +  "description": "The one-time token from the preview. Only use it after the user has said yes.",
      +  "type": "string"
      +}
  2. Changed5 schema fields changedv1.0.2
    • addedInput schema / properties / description / description
      Added value: +"Optional description text."
    • addedInput schema / properties / end_at / description
      Added value: +"End time, ISO 8601, e.g. \"2026-11-05T15:00:00-05:00\"."
    • changedInput schema / properties / event_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Calendar event ID (numeric string). Get it from list_calendar_events or list_my_reservations."
    • addedInput schema / properties / start_at / description
      Added value: +"Start time, ISO 8601, e.g. \"2026-11-05T14:00:00-05:00\"."
    • addedInput schema / properties / title / description
      Added value: +"New title. Omit to keep the current one."
  3. First observedv1.0.1

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the ownership restriction and its failure mode, the partial-update contract ('Fields you omit stay the same'), and the two-phase preview/confirm_token protocol. These are exactly the behavioral facts an agent needs before invoking a destructive mutation.

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-loads the core action and scope in the first sentence, then the mutation semantics, then the confirmation protocol. The bracketed confirmation paragraph is long but every clause carries operational weight; minor tightening is possible.

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, open-world mutation with no output schema, the description covers ownership, partial-update behavior, and the confirmation handshake. It leaves unstated what happens to recurring events or whether attendees are notified, which keeps it from a 5.

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; the description adds real meaning by explaining that omitted fields are preserved and by framing confirm/confirm_token as a paired, second-call-only mechanism. It does not add format detail for the time fields, which the schema already covers.

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 ('Change the title, times or description of a calendar event') plus a scope qualifier ('you created'), which cleanly separates it from create_personal_event and delete_calendar_event in the sibling list.

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 a clear when-not condition ('Only events you own can be changed; course events return a permission error') and a full when-to-use protocol for the confirmation flow. It does not name a sibling alternative for creating or deleting events, so it stops short of a 5.

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