well_update_calendar_event

shallow

io.github.WellApp-ai/well-mcp · Verify this server

Change an event on one of the user's own Google calendars: its title, time, guests, place, description or repeat rule. Use this tool when the user asks to move, rename, reschedule or change a meeting. Find the event first with well_list_calendar_events or well_get_calendar_event. Skip the lookup only when the user gave its event_id and either the event is not repeating or the user gave the exact start of the occurrence. REQUIRED: event_id, scope, notify_attendees. Send only the fields that change. scope is "occurrence" to change just one meeting of a repeating event, or "series" for all of them; for a single event either value changes that event. For one occurrence of a repeating event, also send occurrence_start, a timestamp with an offset (2026-10-12T10:00:00+02:00): the exact start the user gave, or else the occurrence_start value the list returned for it. Never guess it: if the user gave only a day, look the occurrence up with well_list_calendar_events first. For a repeating event, ask the user whether they mean this one occurrence or the whole series, and pass their answer as scope. Never assume it. Ask the user whether the guests should be emailed about the change, and pass their answer as notify_attendees (true or false). Never assume it. Times: start_at and end_at go together, as timestamps with an offset (2026-10-12T10:00:00+02:00) or as dates (2026-10-12) with is_all_day true. The times the user gives are read in the user's zone: send them with the user's offset from well_convert_time and leave timezone out, because the event keeps its own zone. Send timezone, an IANA name (such as Europe/Paris), only with change_timezone true, when the user asks to move the event to another zone. A repeating series keeps its own zone: naming another zone for a series without change_timezone is refused, so send the call again without timezone, unless the user asked to move the series. If a lookup shows the event has no timezone, do not guess one: ask the user, and send the user's zone only after they confirm it. attendees replaces the whole guest list. The repeat rule (recurrence) only changes on the series. Only the user's own calendars can be changed. If the user has not granted calendar access, the call fails with calendar_scope_not_granted and a link: give that link to the user as it is. Returns { success: true, event_id, title, start_at, end_at } on success, or { success: false, error } on failure.

100.0/100

1 trials · measured 3 days ago

well_update_calendar_event scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.WellApp-ai/well-mcp, measured 18 Oct 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
gated
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-10-18100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: well_update_calendar_event
[![Vouch score](https://vouch.tools/api/tools/63e261e2-0028-43d3-a72e-456e41a83863/badge.svg)](https://vouch.tools/tools/63e261e2-0028-43d3-a72e-456e41a83863)
well_update_calendar_event — Vouch