Skip to main content
Glama

Edit a calendar event

event_update

Edit an existing event by updating only specified fields; omitted fields stay unchanged, and null clears description, location, recurrence, or end time.

Instructions

Change fields of an existing event; fields you leave out stay unchanged, and description, location, recurrence and endsAt can be cleared by sending null. Use event_create for a new event and event_delete to remove one. Only the event creator or a flat admin may edit it, otherwise 403 not_owner. For a recurring event the change applies to the whole series; use event_occurrence_change to cancel or move a single date. When the start or allDay changes and the event is still upcoming (or repeating), the other members are notified that it moved. Pass expectedUpdatedAt to guard against concurrent edits: if someone changed the event since, you get 409 event_changed, so read it again with event_get and decide. An endsAt before startsAt fails with ends_before_start. Returns the updated event.

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": "event_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the event to edit, from events_list or event_get.
titleNoNew title.
allDayNotrue to make it an all-day event, false for a timed one. Switching a timed event to all-day without new dates keeps its Berlin dates.
endsAtNoNew end as ISO 8601 datetime with offset, not before the start. null removes the end time.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
locationNoNew place. null clears it; omit to keep it.
startsAtNoNew start as ISO 8601 datetime with offset, year 1900..2200. For an all-day event only the date counts.
recurrenceNoNew repeat rule (format as in event_create). null makes it a one-off event.
descriptionNoNew details. null clears them; omit to keep the current text.
expectedUpdatedAtNoThe updatedAt value you last read from event_get or events_list. When set, the edit only applies if the event is unchanged since; otherwise 409 event_changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / recurrence / anyOf
      Previous value: -[
      -  {
      -    "description": "Repeat rule, an RFC 5545 subset with parts separated by \";\", for example \"FREQ=WEEKLY;BYDAY=MO,TH;COUNT=10\". FREQ=DAILY|WEEKLY|MONTHLY|YEARLY is required; optional INTERVAL 1..365, BYDAY (MO..SU), COUNT 1..366, UNTIL. Anything else fails with recurrence_invalid.",
      -    "maxLength": 200,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 200,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Changed10 schema fields changedv0.1.1
    • addedInput schema / properties / allDay / description
      Added value: +"true to make it an all-day event, false for a timed one. Switching a timed event to all-day without new dates keeps its Berlin dates."
    • addedInput schema / properties / description / description
      Added value: +"New details. null clears them; omit to keep the current text."
    • addedInput schema / properties / endsAt / description
      Added value: +"New end as ISO 8601 datetime with offset, not before the start. null removes the end time."
    • addedInput schema / properties / expectedUpdatedAt / description
      Added value: +"The updatedAt value you last read from event_get or events_list. When set, the edit only applies if the event is unchanged since; otherwise 409 event_changed."
    • addedInput schema / properties / id / description
      Added value: +"Id of the event to edit, from events_list or event_get."
    • addedInput schema / properties / location / description
      Added value: +"New place. null clears it; omit to keep it."
    • changedInput schema / properties / recurrence / anyOf
      Previous value: -[
      -  {
      -    "description": "RFC 5545 subset, separated by \";\": FREQ=DAILY|WEEKLY|MONTHLY|YEARLY (required), INTERVAL 1..365, BYDAY (MO..SU), COUNT 1..366, UNTIL. Otherwise recurrence_invalid.",
      -    "maxLength": 200,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "Repeat rule, an RFC 5545 subset with parts separated by \";\", for example \"FREQ=WEEKLY;BYDAY=MO,TH;COUNT=10\". FREQ=DAILY|WEEKLY|MONTHLY|YEARLY is required; optional INTERVAL 1..365, BYDAY (MO..SU), COUNT 1..366, UNTIL. Anything else fails with recurrence_invalid.",
      +    "maxLength": 200,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / recurrence / description
      Added value: +"New repeat rule (format as in event_create). null makes it a one-off event."
    • addedInput schema / properties / startsAt / description
      Added value: +"New start as ISO 8601 datetime with offset, year 1900..2200. For an all-day event only the date counts."
    • addedInput schema / properties / title / description
      Added value: +"New title."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false; the description goes far beyond that with partial-update semantics, null-to-clear rules, an authorization model (creator or flat admin, else 403 not_owner), whole-series scope for recurring events, notification side effects on start/allDay changes, 409 event_changed concurrency behavior, and the ends_before_start validation failure. Return behavior ("Returns the updated event") is also disclosed despite no output schema.

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-loaded with the core mutation semantics, then permission, recurrence scope, side effects, concurrency, and validation in a sensible order. It is dense and semicolon-chained, so it reads as a block rather than clearly separated clauses, but nearly every sentence carries distinct information.

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?

Covers a 10-parameter mutation tool with no output schema: partial updates, clearing, permission failure, series scope, notification side effects, optimistic concurrency, and validation errors are all addressed. Nothing an agent needs in order to call this correctly is missing.

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, and the description adds the cross-parameter rule that omitted fields stay unchanged while null clears description, location, recurrence, and endsAt. The interplay between startsAt/allDay changes and notification, and the purpose of expectedUpdatedAt, is reinforced rather than merely restated. Not a 5 because the per-parameter details largely duplicate the already-thorough schema.

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 existing event") and immediately distinguishes itself from event_create, event_delete, and event_occurrence_change. An agent can pick this tool out of the calendar family without opening the 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 when-to-use alternatives: event_create for new events, event_delete for removal, event_occurrence_change for a single date of a series, and event_get re-read after a 409. It also states the concurrency-guard workflow (pass expectedUpdatedAt, on 409 re-read and decide), which is actionable routing guidance rather than inference.

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