intervals-icu-mcp

by hhopke

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

icu_create_event

Create one Intervals.icu calendar event from scratch, including structured workouts, notes, races, or multi-day blocks.

Instructions

Create ONE new calendar event from scratch.

For two or more events in a single call, prefer icu_bulk_create_events over a loop. For copying existing events forward in time (repeating a workout for N weeks), use icu_duplicate_events — that tool reuses an existing event's payload instead of taking new fields.

For category guidance and the training_availability enum, read the intervals-icu://event-categories resource. For structured WORKOUT events, put workout-syntax text in description — see intervals-icu://workout-syntax.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Event name
`tags`	No	Calendar tags for grouping and filtering, without the leading # (e.g. ["sweet-spot", "indoor"])
`color`	No	Custom display color (hex string)
`category`	Yes	Event category enum. Common: WORKOUT, NOTE, RACE_A/B/C, TARGET, PLAN, HOLIDAY, SICK, INJURED. Full list with use-case guidance and the training_availability enum: intervals-icu://event-categories resource. Legacy aliases RACE→RACE_A, GOAL→TARGET accepted.
`end_date`	No	End date in YYYY-MM-DD format. Use for ranged categories (INJURED, SICK, HOLIDAY, SEASON_START) to mark a multi-day block.
`athlete_id`	No	Athlete ID (for coaches managing multiple athletes)
`event_type`	No	Activity discipline (NOT the category): Ride, Run, Swim, Walk, Hike, WeightTraining, Workout, VirtualRide, VirtualRun, Other (full discipline list: intervals-icu://event-categories resource). Required for RACE_A/B/C events.
`start_date`	Yes	Start date in YYYY-MM-DD format
`description`	No	Event description (plain text for non-workouts). 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 marker on the fitness chart
`training_load`	No	Planned training load
`distance_meters`	No	Planned distance in meters
`duration_seconds`	No	Planned 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 entirely from the fitness chart
`training_availability`	No	Training availability: NORMAL, LIMITED, or UNAVAILABLE. Typical for INJURED/SICK/HOLIDAY blocks.

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": "Calendar tags for grouping and filtering, without the leading # (e.g. [\"sweet-spot\", \"indoor\"])"
+}

Changed1 schema field changedv5.0.1Sep 11, 2026

changedInput schema / properties / event_type / description

Previous value: -"Activity discipline (NOT the category): Ride, Run, Swim, Walk, Hike, VirtualRide, VirtualRun, Other. Required for RACE_A/B/C events."New value: +"Activity discipline (NOT the category): Ride, Run, Swim, Walk, Hike, WeightTraining, Workout, VirtualRide, VirtualRun, Other (full discipline list: intervals-icu://event-categories resource). Required for RACE_A/B/C events."

Changed1 schema field changedv4.3.2Jul 25, 2026

changedInput schema / properties / description / description

Previous value: -"Event description. For WORKOUT events, use Intervals.icu structured workout syntax (see intervals-icu://workout-syntax resource) — the server parses it into a structured workout with training load and zones."New value: +"Event description (plain text for non-workouts). 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."

Changed5 schema fields changedv3.0.0May 20, 2026

changedInput schema / properties / category / description

Previous value: -"Event category. WORKOUT, NOTE, RACE_A/RACE_B/RACE_C (race tier), TARGET (performance goal), PLAN, HOLIDAY (Urlaub), SICK (Krank), INJURED (Verletzt), SET_EFTP, FITNESS_DAYS (Fitnesstage), SEASON_START (Saison), SET_FITNESS. Legacy aliases RACE→RACE_A and GOAL→TARGET are accepted."New value: +"Event category enum. Common: WORKOUT, NOTE, RACE_A/B/C, TARGET, PLAN, HOLIDAY, SICK, INJURED. Full list with use-case guidance and the training_availability enum: intervals-icu://event-categories resource. Legacy aliases RACE→RACE_A, GOAL→TARGET accepted."

changedInput schema / properties / description / description

Previous value: -"Event description. For WORKOUT events, use Intervals.icu structured workout syntax to define intervals, targets, and structure. The server automatically parses this into a structured workout. Read the intervals-icu://workout-syntax resource for the complete syntax reference. Example: 'Warmup\n- 10m ramp 50%-75%\n\nMain Set 3x\n- 5m 95%\n- 3m 55%\n\nCooldown\n- 10m 50%'"New value: +"Event description. For WORKOUT events, use Intervals.icu structured workout syntax (see intervals-icu://workout-syntax resource) — the server parses it into a structured workout with training load and zones."

changedInput schema / properties / end_date / description

Previous value: -"End date in YYYY-MM-DD format. Use for ranged categories like INJURED, SICK, HOLIDAY, SEASON_START to mark a multi-day block."New value: +"End date in YYYY-MM-DD format. Use for ranged categories (INJURED, SICK, HOLIDAY, SEASON_START) to mark a multi-day block."

changedInput schema / properties / event_type / description

Previous value: -"Activity discipline (NOT the category). Must be one of: Ride, Run, Swim, Walk, Hike, VirtualRide, VirtualRun, Other. Required for RACE_A/RACE_B/RACE_C events — the API rejects races without a discipline."New value: +"Activity discipline (NOT the category): Ride, Run, Swim, Walk, Hike, VirtualRide, VirtualRun, Other. Required for RACE_A/B/C events."

changedInput schema / properties / training_availability / description

Previous value: -"Training availability during the event: NORMAL (Verfügbar), LIMITED (Begrenzt), or UNAVAILABLE (Nicht verfügbar). Typical for INJURED/SICK/HOLIDAY blocks so the planner skips or scales workouts."New value: +"Training availability: NORMAL, LIMITED, or UNAVAILABLE. Typical for INJURED/SICK/HOLIDAY blocks."

First observedv0.1.0May 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations cover the safety profile (not read-only, not idempotent, not destructive), so the bar is lower. The description still adds genuine behavioral context beyond them: this tool takes new field values rather than reusing an existing event payload, and it discloses that WORKOUT bodies go through server-side parsing of workout-syntax text. It does not, however, restate the non-idempotent write nature explicitly.

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?

Front-loaded with the single most decision-relevant fact (creates ONE event), followed by alternative routing and then resource pointers. Four short paragraphs, no filler, though the two resource references could be tightened into one sentence.

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 an 18-parameter mutation tool with 100% schema coverage, an output schema, and full annotations, the description supplies the routing and resource context an agent needs. Nothing critical is missing, though it says nothing about the shape of a successful response or error behavior, which is acceptable given the output schema exists.

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%, so the baseline is 3. The description largely duplicates schema-level guidance (pointing at intervals-icu://event-categories and intervals-icu://workout-syntax for category and workout text) rather than adding semantics the schema lacks; the richer detail (silent drops, repeat blocks) lives in the schema, not here.

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?

States a specific verb and resource with an explicit scope constraint: "Create ONE new calendar event from scratch." It immediately distinguishes itself from sibling creation tools (icu_bulk_create_events, icu_duplicate_events) without the agent needing to open any schema.

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

Usage Guidelines5/5

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

Explicit routing rules: use this for a single event, prefer icu_bulk_create_events for 2+, and icu_duplicate_events when copying an existing payload forward in time. It also names the required resource reads (intervals-icu://event-categories, intervals-icu://workout-syntax) and when each applies.

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

Deploy Server