intervals-icu-mcp

Overview Schema Source Related Servers Discussions Admin

icu_update_event

Idempotent

Update an existing Intervals.icu calendar event by changing only the fields you pass; other fields remain unchanged. Adjust dates, workout details, tags, and visibility.

Instructions

Update an existing calendar event.

Only fields you pass are sent — other fields remain unchanged. For category and training_availability semantics, see intervals-icu://event-categories. For WORKOUT description syntax, see intervals-icu://workout-syntax.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Updated event name
`tags`	No	Replacement tag list, without the leading # — overwrites existing tags, so include any to keep. [] clears
`color`	No	Updated color (hex string)
`end_date`	No	Updated end date (YYYY-MM-DD)
`event_id`	Yes	Event ID to update
`athlete_id`	No	Athlete ID (for coaches managing multiple athletes)
`event_type`	No	Updated activity type
`start_date`	No	Updated start date (YYYY-MM-DD)
`description`	No	Updated description. For WORKOUT events the server parses this into structured, device-syncable steps with zones and a training load. Use Intervals.icu workout syntax: one step per line as '- <duration> <target>' (duration FIRST), grouped under Warmup / Main / Cooldown headers. Targets: bike '- 5m 85%', '- 5m Z4', or absolute '- 5m 210w'; HR '- 10m 70-80% HR' or '- 10m 145bpm'; run/swim pace '- 5m Z2 Pace', absolute only with a trailing 'pace' word: '- 5m 4:45/km pace', '- 200mtr 1:45/100m pace' (bare '5:00/km' or '1:45/100m' silently drops); threshold is relative — run '- 25m 100% pace', swim CSS '- 200mtr 100% pace' — the words 'threshold'/'CSS'/'5K pace' are NOT parsed as targets. Add cadence to any step: '- 3m Z2 90rpm'. No target: '- 20m free'. Repeats: put 'Nx' after a section name with steps flat beneath, and leave a blank line before and after the repeat block (without it the repeat silently runs only once) — e.g. 'Main 5x' then '- 3m 110%' / '- 3m 50%'. Ramps: '- 10m ramp 50-70%'. Rest: append 'Ns rest' to a step ('- 200mtr Z2 20s rest') or use a separate '- 20s intensity=rest' step (only intensity=rest exports as a device rest step) — never a bare '- 20s' step (that becomes work, not rest). Durations: 'm'=minutes, 's'=seconds; distance steps use 'mtr'=meters / 'km' / 'yrd' (e.g. swim '- 400mtr Z2 Pace'). Do NOT write '[repeat 5x ...]', nested bullets, or 'Z5 3m' (target before duration). Runs need a pace or HR target — a bare 'Z2' gives no load. Full reference: intervals-icu://workout-syntax resource.
`show_as_note`	No	Show event as a note on the fitness chart
`training_load`	No	Updated training load
`distance_meters`	No	Updated distance in meters
`duration_seconds`	No	Updated duration in seconds
`show_on_ctl_line`	No	Render event on the CTL line
`hide_from_athlete`	No	Hide this event from the athlete's calendar (the web UI's 'Hide from athlete' checkbox). For coaches managing an athlete via athlete_id
`athlete_cannot_edit`	No	Lock this event so the athlete cannot move or edit it (the web UI's 'Athlete cannot edit' checkbox). For coaches managing an athlete via athlete_id
`not_on_fitness_chart`	No	Hide event from the fitness chart
`training_availability`	No	Updated training availability: NORMAL, LIMITED, or UNAVAILABLE

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv5.4.0Sep 30, 2026

addedInput schema / properties / athlete_cannot_edit

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Lock this event so the athlete cannot move or edit it (the web UI's 'Athlete cannot edit' checkbox). For coaches managing an athlete via athlete_id"
+}

addedInput schema / properties / hide_from_athlete

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Hide this event from the athlete's calendar (the web UI's 'Hide from athlete' checkbox). For coaches managing an athlete via athlete_id"
+}

Changed1 schema field changedv5.2.0Sep 24, 2026

addedInput schema / properties / tags

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Replacement tag list, without the leading # — overwrites existing tags, so include any to keep. [] clears"
+}

Changed1 schema field changedv4.3.2Jul 25, 2026

changedInput schema / properties / description / description

Previous value: -"Updated description"New value: +"Updated description. For WORKOUT events the server parses this into structured, device-syncable steps with zones and a training load. Use Intervals.icu workout syntax: one step per line as '- <duration> <target>' (duration FIRST), grouped under Warmup / Main / Cooldown headers. Targets: bike '- 5m 85%', '- 5m Z4', or absolute '- 5m 210w'; HR '- 10m 70-80% HR' or '- 10m 145bpm'; run/swim pace '- 5m Z2 Pace', absolute only with a trailing 'pace' word: '- 5m 4:45/km pace', '- 200mtr 1:45/100m pace' (bare '5:00/km' or '1:45/100m' silently drops); threshold is relative — run '- 25m 100% pace', swim CSS '- 200mtr 100% pace' — the words 'threshold'/'CSS'/'5K pace' are NOT parsed as targets. Add cadence to any step: '- 3m Z2 90rpm'. No target: '- 20m free'. Repeats: put 'Nx' after a section name with steps flat beneath, and leave a blank line before and after the repeat block (without it the repeat silently runs only once) — e.g. 'Main 5x' then '- 3m 110%' / '- 3m 50%'. Ramps: '- 10m ramp 50-70%'. Rest: append 'Ns rest' to a step ('- 200mtr Z2 20s rest') or use a separate '- 20s intensity=rest' step (only intensity=rest exports as a device rest step) — never a bare '- 20s' step (that becomes work, not rest). Durations: 'm'=minutes, 's'=seconds; distance steps use 'mtr'=meters / 'km' / 'yrd' (e.g. swim '- 400mtr Z2 Pace'). Do NOT write '[repeat 5x ...]', nested bullets, or 'Z5 3m' (target before duration). Runs need a pace or HR target — a bare 'Z2' gives no load. Full reference: intervals-icu://workout-syntax resource."

First observedv0.1.0May 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, and openWorld=true, so the safety profile is covered. The description adds the key behavioral trait annotations cannot express — that this is a sparse/patch update where omitted fields are preserved — which materially affects how an agent should call it.

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?

Three short sentences, front-loaded with the action and the patch constraint before the resource pointers. Efficient, though the two resource references partially duplicate pointers already embedded in the schema's 'description' and 'training_availability' fields.

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 mutation tool with full annotation coverage, a complete output schema, and 100% schema documentation on 18 params, the description supplies what structured data cannot: sparse-update semantics and resource pointers for the two semantically complex fields. No critical gap for an agent to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100% across all 18 parameters, including the extensive inline workout-syntax documentation on 'description', so the schema carries the full parameter burden. The description only re-points at intervals-icu://workout-syntax and intervals-icu://event-categories, which the schema already references, adding no new parameter meaning.

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

Purpose4/5

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

States a specific verb+resource ('Update an existing calendar event'), which clearly separates it from icu_create_event, icu_delete_event, and icu_bulk_* siblings. It does not explicitly name a sibling to disambiguate against (e.g. icu_update_workout vs icu_update_event), but the resource is unambiguous.

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

Usage Guidelines3/5

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

The patch-semantics sentence ('Only fields you pass are sent — other fields remain unchanged') is genuine usage guidance for a partial-update tool, and it points to two resources for edge semantics. However, it never states when to choose this tool over icu_update_workout, icu_bulk_update_event_access, or icu_create_event, so the routing is left to inference.

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

Deploy Server