Set calendar event
set_calendar_eventAdd an event to a project's calendar, or change the one named by 'id' — the WHOLE of it as you write it: what you leave out of a change is cleared. 'start' and 'end' are the FIRST occurrence; a time without an offset (2026-11-23T18:00) is read on the 'timeZone' clock (default: yours). 'recurrence' repeats it, as an RFC 5545 RRULE: FREQ=DAILY or FREQ=WEEKLY, INTERVAL, BYDAY (MO,TU,…), and UNTIL or COUNT — 'FREQ=WEEKLY;BYDAY=MO' is every Monday at the start's time, kept across summer time. Without 'id', an 'externalId' the project already has changes that event instead of adding another, so writing your schedule again does not double it ('created' says which). Changing a series drops the changes of occurrences its new rule no longer gives. 'layoutMatters' with 'layout' gives it a configuration of its room: where each unit of equipment has to stand when it begins — a reconfiguration is then worked out before it wherever the units stand elsewhere (list_reconfigurations). Where the project has a weekly ceiling of reconfigurations, a write that takes a week over it is refused and undone, naming the week ('overCeiling'), unless somebody who configures the project writes it with confirmOverCeiling=true — or allowed that week first (approve_reconfigurations). Anybody who may write in the project. Answers the event as written.
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>",
"title": "<title>",
"start": "<start>",
"end": "<end>"
},
"name": "set_calendar_event"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | The event to change, as list_calendar_events gives 'eventId'. Leave out to add one. | |
| end | Yes | The first occurrence's end, the same way; every occurrence lasts as long. At most 31 days after the start. | |
| 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. | |
| start | Yes | The first occurrence's start, ISO 8601: 2026-11-23T18:00 (on 'timeZone') or with an offset. | |
| title | Yes | The event's title, e.g. 'Rhythmics'. | |
| labels | No | Labels as 'a,b' — what a subscription to part of the calendar is cut by. | |
| layout | No | Its configuration: units of equipment and their points in millimetres, 'resourceId:x:y' separated by commas, e.g. '12:1200:300,13:400:800'. A unit placed is a unit it takes. Leave out to keep; an empty string clears it. | |
| people | No | Who it is with, as logins 'a,b' (list_users) — members of the project, or somebody its dates were opened to: each of them then sees this event among their dates. Leave out to keep who it has; an empty string takes them all off. | |
| source | No | Who you are, as the history should say it — 'solver', 'bot'. The door (mcp) and your account are recorded anyway. | |
| project | Yes | The project key, e.g. TH. | |
| issueKey | No | An issue the event is about, e.g. 'TH-12'. | |
| location | No | Where it happens, e.g. 'Hall'. | |
| timeZone | No | IANA time zone the times and the repeat are on, e.g. Asia/Yerevan. Default: yours. | |
| resources | No | The rooms and units it takes, as resource ids 'a,b' (list_resources). Leave out to keep what it has; an empty string takes them all off. A resource under repair cannot be newly given. | |
| externalId | No | Your own id for it (a bot's, a solver's), unique in the project; writing it again changes the same event. | |
| recurrence | No | RRULE to repeat it, e.g. 'FREQ=WEEKLY;BYDAY=MO' or 'FREQ=WEEKLY;BYDAY=MO,WE;UNTIL=20270630'. Leave out for once. | |
| description | No | Free text, Markdown. | |
| layoutMatters | No | true: its room's configuration matters — its units have to stand at 'layout' when it begins. Leave out to keep what it has. | |
| confirmOverCeiling | No | true to let this write take a week over the ceiling of reconfigurations — only for somebody who configures the project. |