Skip to main content
Glama

Update event

update_event

Modify an existing calendar event you organize by changing only the fields you specify, such as time, subject, location, or attendees, with optional updates sent to attendees.

Instructions

Change an event you organize. Only given fields change; attendee lists replace the existing ones. For meetings, attendees are sent an update unless notifyAttendees is false.

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
endNoEnd. ISO 8601. With an offset (2026-11-02T14:00:00Z or +01:00) it is exact; without one it is local time in timeZone, or in the mailbox time zone if timeZone is omitted. For all-day events the day after the last day (exclusive)
bodyNoDescription / agenda
startNoStart. ISO 8601. With an offset (2026-11-02T14:00:00Z or +01:00) it is exact; without one it is local time in timeZone, or in the mailbox time zone if timeZone is omitted. For all-day events a date (YYYY-MM-DD)
showAsNoFree/busy status
subjectNoTitle
isAllDayNoAll-day event
locationNoLocation text
timeZoneNoIANA time zone for start/end without an offset, e.g. "Europe/London"
attendeesNoRequired attendees: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
bodyFormatNoBody format: "text" (default) or "html"
categoriesNoCategory names
sensitivityNo
notifyAttendeesNoSend updates to attendees (default true)
optionalAttendeesNoOptional attendees: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
reminderMinutesBeforeNoReminder in minutes before start; null disables the reminder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true. The description adds genuinely useful behavior beyond them: fields absent from the request are left unchanged, attendee arrays are wholesale replacements rather than merges, and meeting updates trigger notification emails unless notifyAttendees=false. It does not cover failure modes (missing event, insufficient permissions) or whether a replacement attendee list is recoverable.

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?

Three short sentences, each carrying distinct information: identity/scope first, mutation semantics second, side effects third. No filler and no repetition of schema content.

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 16-parameter mutation with no output schema, the description covers the highest-risk behaviors (partial update, list replacement, attendee notifications). Gaps remain around error conditions and permission failures, but the rich schema carries most of the remaining burden.

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 94%, so the schema already explains id, start/end offset and timeZone rules, and notifyAttendees defaulting to true. The description's only added meaning is that attendees/optionalAttendees lists replace existing ones rather than append, which is a narrow increment over 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?

"Change an event you organize" states a specific verb (change) and resource (event) plus a scope constraint (only events the user organizes). This implicitly separates it from create_event, delete_event and respond_to_event, though no sibling is named explicitly.

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?

The organizer-only constraint tells the agent when this tool applies and implicitly excludes invitation responses (respond_to_event) and events owned by others. It stops short of naming an alternative or stating what to do for events the user does not organize.

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