Authenticate with the Coros Training Hub API and store the access token.

Authenticate with the Coros mobile API only and store the mobile token.

This is needed for sleep data (deep/light/REM/awake phases) which is only available through the mobile API (apieu.coros.com), not the Training Hub web API.

Check whether valid Coros access tokens are stored locally.

Retrieve nightly HRV and daily metrics from Coros for a configurable time range (up to 24 weeks).

Uses the /analyse/dayDetail/query endpoint which returns daily records including HRV, resting heart rate, training load, and fatigue rate.

Fetch nightly sleep data from Coros for a configurable time range.

Returns per-night sleep stage breakdown (deep, light, REM, awake) and sleep heart rate for each night. Data comes from the Coros mobile API (apieu.coros.com) which is separate from the Training Hub web API.

List Coros activities for a date range.

Fetch full detail for a single Coros activity.

Export a completed Coros activity file and save it locally.

List all saved library workout programs in the Coros account.

Fetch one saved workout program in detail.

Return the checked-in workout builder catalog and enum registry.

The catalog combines:

• static Training Hub enum extraction from public frontend bundles

• live builder correlations captured from Training Hub draft calculate payloads

Return the shared run-step contract used by create_run_workout and update_run_workout.

This includes:

• the plain-step fields accepted by create_run_workout

• the selector + patch fields accepted by update_run_workout

• the checked-in live Training Hub intensity labels and their raw COROS presets

• the human pace input format ('4:05-4:15/km', '5:30/mi') which expands into intensity_type=3 with ms/km intensity_value / intensity_value_extend

Return the shared bike-step contract used by create_bike_workout and update_bike_workout.

This includes:

• the plain-step fields accepted by create_bike_workout

• the selector + patch fields accepted by update_bike_workout

• the checked-in live Training Hub bike intensity labels (if captured) and their raw COROS presets

• the human power input format ('220W', '220-260W') which expands into intensity_type=6 with watts in intensity_value / intensity_value_extend

Return the strength-workout field vocabulary.

This includes:

• the exercise fields accepted by create_strength_workout

• the step_updates patch fields accepted by update_workout when the target is a strength program (strength reuses the generic update_workout tool)

• the target_type aliases ('time', 'reps') and how to look up exercises via list_exercises(sport_type=4)

Use this before authoring or editing a strength workout so the patch vocabulary is explicit rather than guessed.

Create a new structured workout in the Coros account.

The workout appears in the Coros app under Workouts and can be synced to the watch for guided execution.

Create a running workout with explicit run-step semantics.

Use get_run_workout_schema for the exact accepted fields.

Each plain step uses the shared run-step contract:

• kind: warmup, training, rest, cooldown, interval

• target_type: time, distance, or open

• target_duration_seconds or target_distance_meters (omit both for open steps — an open step has no target and runs until the athlete presses the lap button, which is how you author an open warm-up or cool-down)

Optional fields include:

• name

• overview

• intensity_label

• raw intensity fields like intensity_type, hr_type, is_intensity_percent, intensity_percent, intensity_percent_extend, intensity_value, intensity_value_extend, intensity_display_unit

• rest_type

• rest_value

• sets

Repeat groups use:

• repeat

• steps

Repeat groups use:

• repeat

• steps

Notes:

• intensity_label can now use the checked-in live Training Hub labels such as Pace, % Threshold Pace, Heart Rate, or % Max Heart Rate.

• The tool sets COROS running sportType = 1.

Create a cycling workout with explicit bike-step semantics.

Use get_bike_workout_schema for the exact accepted fields.

Each plain step uses the shared bike-step contract:

• kind: warmup, training, rest, cooldown, interval

• target_type: time, distance, or open

• target_duration_seconds or target_distance_meters (omit both for open steps — an open step has no target and runs until the athlete presses the lap button)

Optional fields include:

• name

• overview

• intensity_label (values come from the checked-in live Training Hub bike correlations — common labels: Power, %FTP, Heart Rate, % Max Heart Rate, % Lactate Threshold HR, Cadence, Speed)

• power: human string like '220W' or '220-260W', expands to intensity_type=6 with watts in intensity_value / intensity_value_extend

• raw intensity fields like intensity_type, hr_type, is_intensity_percent, intensity_percent, intensity_percent_extend, intensity_value, intensity_value_extend, intensity_display_unit

• rest_type

• rest_value

• sets

Repeat groups use:

• repeat

• steps

Notes:

• The tool sets COROS cycling sportType = 2.

• If bike intensity_label presets aren't available yet (catalog not captured), pass the raw intensity fields directly or use power.

Clone an existing workout, apply edits, and create a replacement workout.

Sport-agnostic: works for running, cycling, and strength library workouts. For strength-specific field vocabulary and examples, call get_strength_workout_schema. For run-specific schema, use get_run_workout_schema.

This does not mutate the original workout in place. The replacement workout is created in the library, and the caller can optionally delete the old workout afterward.

Clone a running workout, apply run-specific edits, and create a replacement.

Use get_run_workout_schema for the exact accepted fields.

Each update item requires one selector:

• step_index

• step_id

• step_name

After that, it accepts the same run-step fields as create_run_workout, including kind, target_type, target_duration_seconds, target_distance_meters, intensity_label, and the raw COROS intensity fields.

Clone a cycling workout, apply bike-specific edits, and create a replacement.

Use get_bike_workout_schema for the exact accepted fields.

Each update item requires one selector:

• step_index

• step_id

• step_name

After that, it accepts the same bike-step fields as create_bike_workout, including kind, target_type, target_duration_seconds, target_distance_meters, intensity_label, power, and the raw COROS intensity fields.

Delete a workout program from the Coros account.

List planned (scheduled) activities from the Coros training calendar.

List scheduled workout entries in a calendar-friendly format.

These are calendar occurrences, not just library workouts. Each scheduled item carries plan-specific identifiers needed for move/remove/replace flows.

Add an existing workout from the library to the Coros training calendar.

Remove a scheduled workout from the Coros training calendar.

Move a scheduled workout to a new day.

The source-of-truth is the existing scheduled entry identified by (plan_id, id_in_plan). Its embedded program is used to re-schedule on happen_day, which supports both library workouts AND plan-embedded programs from subscribed training plans (which have no library entry).

Order of operations is schedule-new → remove-old, so a failure leaves a duplicate rather than losing the workout. A pre-flight lookup verifies the scheduled entry exists before anything destructive runs.

Replace a scheduled workout by cloning the library workout, applying edits, scheduling the replacement, and removing the old scheduled entry.

Create a new structured strength workout program.

List the exercise catalogue for a given sport type.

Useful for resolving strength/conditioning exercises (sport_type=4) that appear in planned workouts by name and ID.