Set calendar occurrence
set_calendar_occurrenceChange ONE occurrence of a calendar event — move it, retitle it, cancel it — leaving the rest of the series as it is; or with reset=true put it back as the rule gives it. Name it by 'eventId' and 'occurrence' as list_calendar_events gives them (the start its rule gives it, e.g. 20261123T150000Z — the same name after a move). What you leave out keeps what it had; a new 'start' alone keeps its length. An event that happens once has one occurrence and is changed the same way. Subscribers' calendars see the change at their next read. Anybody who may write in the project.
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": {
"project": "<project>",
"eventId": "<eventId>",
"occurrence": "<occurrence>"
},
"name": "set_calendar_occurrence"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | Its new end. | |
| batch | No | Your own name for a set of changes — e.g. 'solver 2026-11-18' — so rollback_calendar_batch can undo all of them in one call. | |
| reset | No | true to drop every change of this one: it is again as the rule gives it. | |
| start | No | Its new start, ISO 8601 (on the event's time zone without an offset). | |
| title | No | Its own title for this one. | |
| source | No | Who you are, as the history should say it — 'solver', 'bot'. The door (mcp) and your account are recorded anyway. | |
| eventId | Yes | The event, as 'eventId'. | |
| project | Yes | The project key, e.g. TH. | |
| location | No | Its own place for this one. | |
| cancelled | No | true to cancel this one, false to bring it back. | |
| occurrence | Yes | The occurrence, as 'occurrence', e.g. 20261123T150000Z. | |
| confirmOverCeiling | No | true to let this write take a week over the ceiling of reconfigurations — only for somebody who configures the project. |