Skip to main content
Glama

Calendar: Update event

calendar_update_event
Destructive

Update explicit fields on a resolved event. Keep event_id paired with the parent calendar_id and do not blindly retry after an ambiguous failure.

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": {
      "calendar_id": "<calendar_id>",
      "event_id": "<event_id>"
    },
    "name": "calendar_update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
bodyNo
startNo
titleNo
notifyNoGoogle-only guest update policy; omit for Microsoft.
event_idYesExact event ID returned by calendar_list_events or calendar_create_event, paired with its parent calendar_id. Calendar event ID: Exact event id in the selected calendar/account. Obtain with: calendar_list_events -> event.id; calendar_create_event -> created event.id Never pass: event title, date.
locationNo
timezoneNoIANA timezone for the event.
attendeesNo
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
conferenceNo
recurrenceNoRFC5545 RRULE, EXRULE, RDATE or EXDATE lines.
visibilityNo
calendar_idYesExact calendar ID returned by calendar_list_calendars; never pass a calendar name. Calendar ID: Exact Google/Microsoft calendar id. Obtain with: calendar_list -> calendar.id Never pass: calendar display name.
transparencyNo
background_colorNo
is_attendees_list_hiddenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / attendees / items / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description adds crucial behavioral context beyond the provided annotations. Specifically, it defines the required state of the event ('resolved') and offers sophisticated operational advice regarding failure handling and retries, which is vital for execution safety.

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 definition is exceptionally concise, using only two well-structured sentences. Every part of the description is functional, providing constraint, context, or risk mitigation advice without any unnecessary wording.

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?

The definition is highly complete given the low schema coverage. It successfully covers the operational limits, required ID relationship, and the state constraints (resolved), which are the most critical pieces of missing information when only looking at the parameters.

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?

Given the low schema coverage (35%), the description adds significant semantic value by explicitly defining the relationship between the 'event_id' and 'parent calendar_id.' This prevents misuse by the agent regarding required inputs, even if the schema defines them separately.

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?

The tool clearly states its purpose: updating explicit fields on a resolved event. While the verb and resource are clear, it relies on the schema to define which fields are 'explicit,' but it successfully differentiates the operation from a general calendar update via the 'resolved event' constraint.

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?

The description provides highly specific usage constraints, mandating that the event_id must be paired with the parent calendar_id. Furthermore, it includes a critical operational guideline advising the agent 'not to blindly retry' after ambiguity, which is essential usage context.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.