Skip to main content
Glama
vcnngr

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calendar_update

Change calendar event details such as title, time, location, description, recurrence, or color for a whole series or a single occurrence while keeping omitted fields unchanged.

Instructions

Change fields of an event (whole series for recurring events, or one occurrence). Omitted fields are kept.

Changing only start keeps the duration; only end/duration_minutes keeps the start. Pass an empty string to clear location/description; rrule='none' turns a series into a single event (its first occurrence). With instance_start only that occurrence of a recurring event changes (e.g. move tomorrow's stand-up): the result is the occurrence's own event (recurrence_exception_of = the series id).

Guests: changing title, time, location, description or recurrence of an event you organise that has guests makes Google e-mail them the update, so it needs confirm=true. Invitations from someone else cannot be changed (only your availability/colour, and reminders with calendar.reminder_*): answer them with calendar.respond / calendar.rsvp.

Avoid rapid successive edits of the same event: an edit made while the sync adapter is uploading the previous one can be overwritten by the server copy (check pending_sync).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoNew end (for all-day: last day, inclusive).
colorNoNew colour name (see calendar.create) or 'default' to reset.
rruleNoNew recurrence rule (e.g. FREQ=WEEKLY;COUNT=4), or 'none' to stop repeating.
startNoNew start (same formats as calendar.create).
titleNoNew title.
all_dayNoConvert to/from an all-day event.
confirmNoRequired (true) when the change is e-mailed to guests (event you organise with guests).
event_idYesEvent id (for one occurrence: the series id, plus instance_start).
locationNoNew location ('' clears it).
timezoneNoIANA zone for the new times (default: the event's zone, else Europe/Rome).
descriptionNoNew description ('' clears it).
availabilityNobusy / free / tentative.
instance_startNoChange only this occurrence of a recurring event: its start as listed by calendar.events (or its date).
duration_minutesNoNew length in minutes (alternative to end).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does: guest e-mail side effects requiring confirm=true, permission limits on foreign invitations, and a concurrency hazard (rapid successive edits can be overwritten by the server; check pending_sync). It also discloses that instance_start produces a new occurrence object with recurrence_exception_of set.

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 action, then grouped into labelled paragraphs (recurrence, clearing, guests, sync hazard) that an agent can scan selectively. Dense but essentially waste-free; the parenthetical examples ('e.g. move tomorrow's stand-up') earn their space by anchoring the semantics.

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?

For a 14-parameter mutation tool with no annotations and no output schema, the description covers mutation scope, confirmation auth, permission boundaries, recurrence edge cases, and even the shape of the returned occurrence. Nothing an agent needs to call it 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, but the description adds genuine cross-parameter meaning the schema cannot express: start-only keeps duration, end/duration_minutes keeps start, empty string clears location/description, rrule='none' demotes a series to a single event at its first occurrence. Only timezone/all_day/color semantics are left entirely to the 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?

Opens with a specific verb+resource: 'Change fields of an event', and immediately narrows scope ('whole series for recurring events, or one occurrence'). It also names the sibling it competes with ('answer them with calendar.respond / calendar.rsvp'), so an agent can distinguish it from calendar_create and the RSVP tools without reading schemas.

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?

Explicit inclusions and exclusions: use instance_start to move one occurrence, use calendar.respond/calendar.rsvp for invitations you don't organise. It even states the narrow legal subset of edits on third-party invitations (availability/colour, calendar.reminder_*), which is exactly the routing decision an agent must make.

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