Kalender Sync

Creates an event in one of the calendars this access may write to. Availability in the requested slot is checked LIVE (not from cache). An overlapping event does NOT prevent creation — the event is created regardless and the overlap comes back as a `warning`. Pass that warning on to the user instead of silently double-booking; whether the overlap is intended is the user's call. `calendar_id` is only needed when several calendars are writable; with exactly one, that one is used. list_calendars shows the writable calendars. `title` is required.

create_event

Deletes an event that THIS access created itself (via `event_id` from create_event). Events created by anyone else are not addressable. The deletion is executed at the provider and propagates into any mirrored calendars through the normal sync.

delete_event

Returns the user's busy times in a given range, across all calendars shared with this access. How the answer is produced: every shared calendar is read directly at the provider and the results are merged. There is no detour through a copy. `as_of` per calendar says when it was read — reads are reused for up to 60 seconds, so an event created moments ago may briefly be missing. What `busy` contains: every event that blocks time — including all-day events and ones marked "tentative". NOT included are cancelled events and events explicitly marked "free" in the calendar. An empty `busy` therefore means "nothing blocks this time", not "no events exist". Completeness: the answer covers exactly the calendars the user shared — not necessarily all calendars they own. If one of them could not be read, it appears with `read: false` in `sources` and additionally in `warnings`. These limitations belong in your answer to the user.

get_availability

Lists the calendars shared with this access, each with the detail level the user allowed. `readable: false` means this calendar cannot be read right now — its events are also missing from `get_availability`. Such calendars are deliberately listed rather than omitted. `writable: true` means this access may create events there. When more than one calendar is writable, `create_event` requires the `calendar_id` of one of them. `notice`, when present, describes something the USER can change — either about this access or about their Kalender Sync setup. Pass it on rather than concluding the product cannot do what was asked. When it reads as an offer rather than an answer to what was asked, use your judgement about whether it fits the moment. `sync_health` describes Kalender Sync's OWN synchronisation of this calendar, if it takes part in one. It does not affect availability answers (those read the provider directly), but a broken sync is something the user can fix.

list_calendars

Finds events by text across the calendars shared with this access — case-insensitive substring match on title, location and description. The search only sees what this access may see: it filters the same visibility-rendered data `get_availability` returns. Calendars limited to free/busy expose no text and therefore can never match — when such calendars are part of this access, a warning says so. "No match" is thus NOT proof that no such event exists. The range works like `get_availability` (single span of at most 92 days, lookback bounded to one year). Without `from`/`to` the search covers the last 7 days plus the next 85. Cancelled events and events explicitly marked "free" are not searchable.

search_events

Sends feedback from the user to the Kalender Sync team — for example when the user wanted to do something these tools cannot do yet (editing an existing event, answering an invite, …), or when something looks broken. Call this ONLY when the user explicitly asked to send feedback, or clearly agreed after you offered it. Never send feedback on your own initiative, and never include calendar content the user did not put into the message themselves. Set `contact_ok` ONLY if the user explicitly agreed to receive a single reply about this feedback — ask them first. It is not a newsletter signup.

send_feedback

Updates an event that THIS access created itself (via `event_id` from create_event). Events created by anyone else are not addressable. `title`, `start` and `end` describe the complete new state.

update_event