Skip to main content
Glama

Set calendar event

set_calendar_event
Destructive

Add 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

NameRequiredDescriptionDefault
idNoThe event to change, as list_calendar_events gives 'eventId'. Leave out to add one.
endYesThe first occurrence's end, the same way; every occurrence lasts as long. At most 31 days after the start.
batchNoYour 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.
startYesThe first occurrence's start, ISO 8601: 2026-11-23T18:00 (on 'timeZone') or with an offset.
titleYesThe event's title, e.g. 'Rhythmics'.
labelsNoLabels as 'a,b' — what a subscription to part of the calendar is cut by.
layoutNoIts 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.
peopleNoWho 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.
sourceNoWho you are, as the history should say it — 'solver', 'bot'. The door (mcp) and your account are recorded anyway.
projectYesThe project key, e.g. TH.
issueKeyNoAn issue the event is about, e.g. 'TH-12'.
locationNoWhere it happens, e.g. 'Hall'.
timeZoneNoIANA time zone the times and the repeat are on, e.g. Asia/Yerevan. Default: yours.
resourcesNoThe 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.
externalIdNoYour own id for it (a bot's, a solver's), unique in the project; writing it again changes the same event.
recurrenceNoRRULE to repeat it, e.g. 'FREQ=WEEKLY;BYDAY=MO' or 'FREQ=WEEKLY;BYDAY=MO,WE;UNTIL=20270630'. Leave out for once.
descriptionNoFree text, Markdown.
layoutMattersNotrue: its room's configuration matters — its units have to stand at 'layout' when it begins. Leave out to keep what it has.
confirmOverCeilingNotrue to let this write take a week over the ceiling of reconfigurations — only for somebody who configures the project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / people
      Added value: +{
      +  "default": null,
      +  "description": "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.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / batch
      Added value: +{
      +  "default": null,
      +  "description": "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.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / source
      Added value: +{
      +  "default": null,
      +  "description": "Who you are, as the history should say it — 'solver', 'bot'. The door (mcp) and your account are recorded anyway.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. Changed3 schema fields changed
    • addedInput schema / properties / confirmOverCeiling
      Added value: +{
      +  "default": false,
      +  "description": "true to let this write take a week over the ceiling of reconfigurations — only for somebody who configures the project.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / layout
      Added value: +{
      +  "default": null,
      +  "description": "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.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / layoutMatters
      Added value: +{
      +  "default": null,
      +  "description": "true: its room's configuration matters — its units have to stand at 'layout' when it begins. Leave out to keep what it has.",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  4. Added

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Substantially exceeds the annotations: it spells out that the write is a full replace ('what you leave out of a change is cleared'), how a changed recurrence drops now-orphaned occurrence overrides, how reconfiguration is computed relative to other placements, that an over-ceiling write is refused and undone with an 'overCeiling' week named, and who is permitted. That is exactly the destructive-mutation detail the hints cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The most consequential fact — full replacement semantics — is front-loaded in the first clause, and most sentences carry unique operational meaning. It is a dense, em-dash-heavy single paragraph with a few stylistic flourishes ('as you write it', 'the door (mcp)') that add length without much information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter mutation tool with no output schema, the description covers the risky behaviors an agent needs: replace-vs-merge, dedupe via externalId, recurrence rule changes, ceiling enforcement and approval escape hatches, and permissions. Only the return payload is left thin ('answers the event as written'), which is a minor omission without a declared output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3; the description adds genuine meaning on top by explaining that start/end define only the FIRST occurrence, that offsetless times are read on the timeZone clock, and that recurrence is an RFC 5545 RRULE kept across summer time. It does not add much beyond the schema for the remaining 15 parameters, so it stops short of 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('Add an event to a project's calendar, or change the one named by id'), explicitly covering both create and update paths, and the externalId rule clarifies how it avoids duplicating rather than creating. An agent can distinguish this from delete_calendar_event or set_calendar_occurrence from the description alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete conditions: leave out 'id' to add, pass 'id' to replace, pass a known 'externalId' to avoid double-writing, use confirmOverCeiling or approve_reconfigurations when over the weekly ceiling. Names the supporting tools (list_reconfigurations, approve_reconfigurations, list_calendar_events). It never states when to use the sibling set_calendar_occurrence for a single occurrence instead, which is the main routing gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources