Skip to main content
Glama
hhopke
by hhopke

icu_update_workout

Idempotent

Modify an existing library workout by updating only the fields you specify, such as name, target, description, color, or training load.

Instructions

Change fields on an EXISTING library workout — only the fields you pass are sent.

To save a new workout use icu_create_workout. This edits the library workout only; calendar events are separate records changed with icu_update_event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNoPLAN folders only: updated day offset from plan start
nameNoUpdated workout name
tagsNoReplacement tag list
colorNoUpdated color (hex string)
indoorNoMark as an indoor workout
targetNoUpdated device target type: AUTO, POWER, HR, or PACE
folder_idNoMove the workout to this folder or plan
athlete_idNoAthlete ID (for coaches managing multiple athletes)
workout_idYesLibrary workout ID (from icu_get_workouts_in_folder)
descriptionNoUpdated workout steps. 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.
workout_typeNoUpdated activity discipline: Ride, Run, Swim, Walk, Hike, WeightTraining, Workout, VirtualRide, VirtualRun, Other (full discipline list: intervals-icu://event-categories resource)
training_loadNoUpdated training load
distance_metersNoUpdated distance in meters
duration_secondsNoUpdated duration in seconds

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds the key behavioral detail that only passed fields are sent (partial update semantics), which is not visible in annotations. It also clarifies that this edits library workouts only, not calendar events. It doesn't discuss auth or rate limits, but the annotations cover the safety profile and the description adds meaningful update semantics.

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

Conciseness5/5

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

The description is two sentences with zero waste. The core function is front-loaded, and the routing guidance is concise. Every sentence earns its place, and the description is appropriately sized for a tool with 14 parameters.

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?

Given the tool's complexity (14 params, output schema present, annotations present), the description is complete enough for an agent to call it correctly. It covers the essential behavioral distinction (partial update, library vs calendar) and routes to the right sibling. The output schema exists, so return values don't need to be described. It could mention idempotency or auth, but annotations already cover the safety profile, so this is a minor gap.

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 description coverage is 100%, so the schema already documents all 14 parameters. The description adds value by explaining the partial-update behavior ('only the fields you pass are sent'), which is critical for understanding how to use the parameters. The description also reinforces the distinction between library workouts and calendar events, which helps interpret parameters like folder_id and workout_id. However, it doesn't add much beyond the schema's per-parameter descriptions, so a 4 is appropriate rather than 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?

The description clearly states the tool's function: 'Change fields on an EXISTING library workout — only the fields you pass are sent.' It explicitly distinguishes from icu_create_workout and icu_update_event, making its scope unambiguous. The verb 'change' plus the resource 'library workout' is specific and differentiates it from siblings.

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?

The description explicitly says when to use this tool vs alternatives: 'To save a new workout use icu_create_workout. This edits the library workout only; calendar events are separate records changed with icu_update_event.' This is clear routing guidance that prevents an agent from confusing library workouts with calendar events or creation with updates.

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

Deploy Server

Other Tools