well_list_calendar_events

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

List the calendar events inside a time range, in start order. Use it when the user asks what is on their calendar, who they meet and when, or before changing an event. A repeating event is expanded into its occurrences inside the range. It returns the events visible to the whole workspace plus the user's own private ones, never another member's private events. Each event has an event_id; a repeating event's occurrences also carry occurrence_start, which well_update_calendar_event and well_delete_calendar_event take to change just that one. To read only the caller's own calendars, pass mine_only: true. Guests are not listed: call well_get_calendar_event for one event's guests. If the result has a note, give it to the user as it is: it invites them to connect their own calendar. The result's connection describes the user's own calendar. Its state is one of "connected" (say nothing about it), "syncing" (the first sync has not finished: say the result can be incomplete), "stale" (say the result can be out of date and give last_synced_at as the time of the last update), "needs_reconnect" (say Well lost access to the calendar, that the result holds only what was synced before, and give reconnect_link once) or "not_connected" (say the user's own calendar is not connected and give reconnect_link once, unless the note already gave it). When the state is not "connected", never call the result complete or up to date, and never call a time free on its strength alone. A null connection means the state could not be read: say nothing about it. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.