Skip to main content
Glama

update_event

Idempotent

Modify an existing calendar event by sending only the fields to change—such as time, title, location, alerts, repeat rules, or calendar—and adjust recurring occurrences with span and confirm.

Instructions

Change fields of an event. Send only the fields to change. An empty string clears 'location', 'notes' or 'url'. Dates are ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00. 'alerts' replaces all alerts, and [] removes them. 'calendar' moves the event to another calendar. Calendar may refuse to move an event to a calendar of another account. For a recurring event, 'span' 'future' changes this and all later occurrences, and it needs 'confirm' true. Changing 'repeat' needs 'span' 'future' (null or frequency 'none' removes the rule). Moving a recurring event to another calendar also needs 'span' 'future'.

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": {
      "id": "<id>"
    },
    "name": "update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEvent id from list_events, search_events or get_event. Recurring events have an id with an @ part. Use it as given.
endNoNew end, after 'start'. ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00
urlNoNew URL. Empty string clears it.
spanNoFor a recurring event: 'this' changes only this occurrence (default), 'future' changes this and all later ones.
notesNoNew notes. Empty string clears them.
startNoNew start. ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00
titleNoNew title.
alertsNoNew alerts, replacing all old ones. [] removes all. Minutes before the start, 0 to 40320, at most 5. For example [10, 1440] is an alert 10 minutes before and one day before.
repeatNoHow the event repeats. Set 'frequency'. 'interval' (1 to 99, default 1) is the gap between repeats. Give 'end' (a date, the last day a repeat can start) or 'count' (1 to 999 occurrences), not both. Without them the event repeats forever. 'days' is only for 'weekly'. Frequency 'none' or null removes the rule.
all_dayNoMake the event all-day or not.
confirmNoMust be true to change a recurring event with 'span' 'future'. It changes all later occurrences.
calendarNoMove the event to this calendar (name or id). Names ignore case.
locationNoNew location. Empty string clears it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The annotations only say it is a non-idempotent-free, non-destructive, local write. The description adds real behavioral detail: field-level clearing semantics, wholesale replacement of alerts, a partial-update model, and the notable warning that the calendar may refuse cross-account moves. It also discloses that confirm=true triggers changes across all future occurrences, which is exactly the kind of consequence an agent must not discover by accident.

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?

The lead sentence front-loads the core contract (partial update) before the edge cases, and the remaining sentences each encode a real rule. It runs long and repeats a few facts the schema already documents (alerts replacement, ISO 8601 examples), which is the only drag on efficiency.

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 13-parameter tool with a nested repeat object and no output schema, the description covers the interaction rules that would otherwise cause silent data damage on recurring events. It does not describe the response or failure behavior (missing id, refused calendar move beyond a warning), but nothing critical to invoking it correctly is absent.

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 schema already carries per-field meaning and the ISO 8601 examples, and much of the description restates it. Where it does add value is the cross-parameter rules the schema only states piecemeal: changing 'repeat' requires 'span': 'future', moving a recurring event likewise, and empty strings act as explicit clearers rather than no-ops.

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 fields of an event') and immediately disambiguates the operation as a partial update ('Send only the fields to change'). This patch semantics cleanly separates it from create_event, delete_event and get_event without needing to name them.

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 concrete conditions for the non-obvious cases: empty string clears location/url/repeat-related fields, alerts replaces rather than appends, recurring changes require 'span': 'future', and that combination requires confirm=true. It does not point to an alternative tool for reading or creating events, but the when-to-use guidance for this tool's own tricky paths is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.