intervals-icu-mcp

Overview Schema Source Related Servers Discussions Admin

Icu Update Event

icu_update_event

Idempotent

Update an existing Intervals.icu calendar event by changing only the fields you provide; all other event details remain unchanged.

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

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

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.9/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, openWorld=true, so the safety profile is covered. The description adds the one non-obvious behavioral fact annotations cannot convey: omitted fields are preserved, so the call is a merge rather than a replace. It omits what happens on an invalid event_id or whether athlete_id is required for coach-scoped edits.

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 key partial-update rule, followed by two pointers to resources. Very efficient. Minor deduction for the 'category' pointer, which references something not in the schema and slightly dilutes the otherwise clean structure.

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?

With 18 parameters, an output schema, and full annotation coverage, this description supplies what structured fields cannot: sparse-update semantics and pointers to the domain references needed for the tricky `description` and `training_availability` values. The residual gap is coach/athlete scoping — nothing explains that `athlete_id` must be set to edit another athlete's event.

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% and the parameter docs are unusually thorough (notably the workout-syntax `description`), so the baseline is 3 and the description adds no parameter-level detail of its own. It also points to a 'category' parameter and 'event-categories' semantics that have no matching property in the schema (the schema exposes `event_type` and `training_availability`), a small dangling reference.

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 and resource ('Update an existing calendar event'), which cleanly distinguishes it from create/delete/get siblings despite the shared icu_*event* namespace. It does not, however, name any sibling or scope boundary (e.g. bulk_update_event_access, update_workout) so the agent must infer the split from the name 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?

'Only fields you pass are sent — other fields remain unchanged' is real usage guidance: it tells the agent this is a sparse PATCH-style update and that omitting a field is safe. It also routes the agent to two reference resources for domain semantics. It stops short of saying when to prefer this over bulk_update_event_access or how it relates to update_workout.

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

Deploy Server