Running Workout

List notes from the athlete's persistent memory, sorted by date descending. Note text is truncated to 300 characters when limit > 10. Returns an empty informative message when no notes match.

list_athlete_notes

List completed activities received via Garmin webhooks or history import. Returns date/time, type, name, duration, distance, avg HR, avg pace and additional fields when available (max HR, bike cadence rpm, swim cadence spm, active lengths, elevation gain D+, calories). Each line ends with the summaryId; when marked [detail available], call get_activity_details for per-lap splits, power and computed metrics. This tool reads local data only — no Garmin API call is made. Activities predating the account connection may be missing unless a history import was run on runningworkout.fr.

list_activities

List workouts scheduled on the Garmin Connect calendar for a given date range (max 62 days). Returns date, workout name, sport, duration, distance, step count, workoutId and scheduleId for each entry. Name, sport, duration, distance and step count are only available for workouts created via Running Workout.

list_scheduled_workouts

Catalogue of the coach's training plans (back to running, 5K, 10K, half-marathon, marathon): length, sessions per week, race or programme, whether a VMA is required, phases. Pass planId to get one plan's sheet plus a preview of one week (default: its peak week) rendered in the athlete's language and units, with paces from their VMA when known — WITHOUT starting anything. Marathon preview: the pace shown is graduated by VMA level only (no goal lookup here) — once actually started with a chrono goalId, start_training_plan anchors it more precisely on the target pace. Use it to show the athlete what a plan looks like before start_training_plan. READ-ONLY.

list_training_plans

Remove a workout from the Garmin Connect calendar (unschedule it). This removes the calendar entry only; the workout itself remains in the Garmin workout library. Use delete_workout to also remove the workout from the library.

delete_scheduled_workout

Reschedule a workout to a different date on the Garmin Connect calendar. Both scheduleId and workoutId are required (the Garmin API requires the workoutId in the update payload).

move_scheduled_workout

Weekly review of the athlete's active plan: each planned session matched with the run recorded that day (done / missed / upcoming, duration, distance, avg HR), other runs, training load (ACWR) and the deterministic decision from the plan's rules (missed sessions → repeat week or not; ACWR → lighten / repeat / as planned). Defaults to the last completed week. READ-ONLY. Then ask the athlete how the week felt (1-5) — pain, illness and heat are YOUR call, not this tool's — write the review with add_athlete_note, and push the next week with schedule_plan_week.

review_plan_week

Create on Garmin Connect and schedule on the Garmin calendar every session of one week of the athlete's active plan (names and descriptions in their language, targets in % VMA resolved from their profile). Sessions already pushed are skipped (never duplicated); sessions whose date is already past are skipped too. Defaults to the current week. Review the week with get_plan_week and the athlete first.

schedule_plan_week

Create or update a structured constraint the training plan must respect. kind: "availability" (which days the athlete can train — pass days), "preference" (e.g. long run on Sunday — pass days), "injury" (a temporary limitation on training — set untilDate when it no longer applies), "equipment" (track access, treadmill, gear), "other". days are ISO weekdays: 1 = Monday … 7 = Sunday. Call WITHOUT constraintId to create; WITH constraintId (from list_athlete_constraints / get_athlete_profile) to update — to end a constraint (limitation lifted, changed schedule) set untilDate to today rather than rewriting it. Only record what the athlete actually said. Rejected with an explicit message on any invalid field (no partial write).

set_athlete_constraint

Create or update one of the athlete's goals — a race or objective with a date, and optionally a distance and a target time. Call WITHOUT goalId to create; WITH goalId (from list_athlete_goals or get_athlete_profile) to update — e.g. set status "done" after the race, "abandoned" if dropped, or adjust targetTimeSec after a reassessment. Only record what the athlete actually stated: never invent a date or a target time. For a chrono goal pass distanceM + targetTimeSec so the target pace can be derived; for a "just finish" goal omit targetTimeSec. Priority A = main goal of the season, B = secondary (default), C = training race. Rejected with an explicit message on any invalid field (no partial write).

set_athlete_goal

Builds the athlete's plan from the parameters they saved on the site. Never asks for or accepts plan parameters. Call once without confirm to get either a link to send the athlete to (no setup yet) or the recap to read back (setup ready) — nothing is written by that first call. Call again with confirm: true only after their explicit go. planId, if passed, only pre-selects a plan on the site's wizard link when no setup exists yet — it never configures anything by itself. All other legacy arguments (raceDate, startDate, variant, days, goalId, longRunMode, replace) are accepted for backward compatibility with clients that still cache the old schema, and silently ignored. Any link in the response is already markdown-formatted (`[text](url)`) — relay it exactly like that so it renders clickable for the athlete: translate the visible words if you like, never touch the URL inside the parentheses, and never retype it as plain text.

start_training_plan

Write one or more declared values to the athlete's persistent memory. Physiological stats (vma_kmh, ftp_watts, fc_max, css_per_100m_sec) are also written to the unified stats history; other keys are declared-only. Validated before writing: unknown key, out-of-range value, wrong unit, future date, or missing/invalid basis cause full rejection (no partial write). Valid keys: weight_kg, height_cm, vma_kmh, fc_max, fc_repos, ftp_watts, css_per_100m_sec, vo2max, weekly_hours_available. IMPORTANT — DO NOT WRITE SILENTLY: You MUST NOT call this tool to record a value you inferred purely from get_athlete_profile's computed figures without one of three real conversational events having happened in this conversation: (1) the athlete told you a test result, (2) you identified an inconsistent sensor recording and the athlete confirmed the correction, or (3) you proposed updating a value based on your own analysis and the athlete explicitly said yes.

set_athlete_data

Update the athlete's active plan: status "done" after the race (then review it with get_activity_details), or a new raceDate to shift the whole calendar (plan rule: the race must stay at least as many full weeks away as the plan needs — shortening a plan is a coaching decision, done by hand). Sessions already pushed to Garmin keep their dates: move them with move_scheduled_workout if needed. Stopping a plan is NOT done here — that is the athlete's own decision, made on the site (see the error message if you pass "abandoned" — legacy, ignored). Any link in the response is already markdown-formatted (`[text](url)`) — relay it exactly like that, never as plain text.

update_training_plan