Fitness, fatigue and wellness
in Intervals.icu, read with AI.
"Am I overreaching?" is a question about several records at once: how much you trained, the fitness and fatigue values Intervals.icu stored on your rides, and what you logged about sleep, resting heart rate, HRV and how tired you felt. An assistant connected through IntervalSync can read all of them and set them side by side by date. It cannot tell you why a number moved.
This is a way to read your own records, not medical advice and not a training prescription. IntervalSync supplies the records; your assistant writes the interpretation, and IntervalSync does not check it.
Where each number comes from
These are all read tools and change nothing; plans and daily limits are on the MCP server page.
- Load, fitness and fatigue:
list_activities. Each completed activity carries its own values. Its default fields includeicu_training_load,icu_ctlandicu_atl, which the review steps call fitness and fatigue. IntervalSync asks Intervals.icu for them and calculates none. With one value per activity, a day without a ride has none.list_activity_fieldslists them under load, and makes no request to Intervals.icu. - Totals by week or month:
get_training_summary. Activity count, distance, time, training load, elevation and calories, with time in power and heart-rate zones, for the last 28 days unless you give dates. Weeks start on Monday, a week with no activity is left out, and the first and last weeks of a range can be part-weeks. It does not returnicu_ctloricu_atl. - Sleep, resting heart rate, HRV, fatigue and notes:
get_wellness. One record per day, newest first, up to 60 days to a page (max_daysallows up to 400), withpagination.next_start_indexpointing to the next, older page. With no dates it reads the last seven days. The names are Intervals.icu's own:restingHR,sleepSecs(seconds) andcommentsfor your notes, withhrv,fatigueandsorenessas written. The code does not list every field a record can hold, so ask the assistant to name the ones it received. - Your profile:
get_athlete_profile. The record Intervals.icu answers with; IntervalSync picks no fields from it. The MCP server page calls it "athlete profile and current training metrics", but the code lists no such metrics, so this article names none. It points to your timezone, which decides where one day ends, and the terms say it carries the weight and resting heart rate you entered there.
Each tool needs its Intervals.icu permission (Activity, Wellness, or Settings for the profile); the support page explains refreshing one that was left out.
Line them up by date
A wellness record is identified by its date, and an activity carries start_date_local, in your own timezone. A ride that starts at nine in the evening can sit on a different day from the HRV you logged the next morning, so ask your assistant which record it paired with which ride. Expect gaps in both directions: a rest day can have a wellness record but no activity, so no fitness or fatigue value, and a ride on a day you logged nothing has the opposite. Nothing in the tools fills either gap.
The catalogue list_activity_fields returns has no field called form. The event-readiness review mentions form but names only icu_ctl and icu_atl for it, and says they can come from get_wellness too; the code's field lists name them only as activity fields. A form figure is your assistant's own arithmetic, and it should show which values it used.
A missing day is missing
The weekly review makes this point too. A wellness field you did not log is left out rather than returned as null, and IntervalSync treats the two as the same: not recorded. A day with no record at all is not in the list, and pagination.total_days counts the records returned, so nine records across a fourteen-day range means five days have none. Neither is evidence of a normal night or a normal resting heart rate.
The values are the ones that were logged, and the tools do not say whether you typed one, a sensor synced it, or an update you confirmed wrote it. update_wellness takes a fatigue score as a whole number from 1 to 10, and nothing in the code says which end is tired; it takes HRV in milliseconds, with no word on how it was measured. Ask which direction and source the assistant assumed.
A prompt that reads and compares
Replace the placeholders with two dates. It asks for records and gaps, not a verdict.
Read my training and wellness records for [START DATE] through [END DATE], and for the same number of days before that. From list_activities, take each activity's date, duration, training load and the fitness and fatigue values Intervals.icu stored on it (icu_ctl and icu_atl). From get_wellness, take whatever sleep, resting heart rate, HRV, fatigue score and notes I logged, and tell me the field names that came back. Put it all in one table by date, newest first. Write "no record" for a date with no wellness record and "not logged" for a field I left empty; do not fill either in or call it normal. State both date windows and how many days in each have a wellness record. Separate what the records show from possible explanations, and say what they cannot tell me. If you calculate anything the tools did not return, show the values you used. Use read tools only and leave my calendar and wellness records unchanged.
It uses two read tools and writes nothing. A wellness value changes only through update_wellness, which refuses to run without your confirmation of the exact values.
Built-in reviews that use these records
get_review_protocol lists six reviews and returns the steps of one: what to look at and which tools to call. It reads nothing from Intervals.icu.
- Ready to train hard? looks at the last 14 days: the last three days of resting heart rate, HRV, sleep and feel against the 14-day baseline, then load, the last hard sessions and
icu_ctlagainsticu_atl, then what is planned. Picked from a prompt menu, it also asks for a go, modify or rest answer; the prompt above stops before that. - The weekly review sets the last 7 days against the three weeks before and reads that week's wellness.
- The 42- and 90-day progress check calls
list_activitiesand nothing else, so sleep and HRV play no part in it. - The block and event reviews read
icu_ctlandicu_atlat the start and end of a block, or over the last eight weeks before an event.
What the records cannot tell you
- One week cannot show a trend. The built-in reviews look back 14 days for a baseline, 28 for the weekly summary, 42 and 90 for a progress check and eight weeks for an event.
- They do not hold the reason. Illness, a poor night, travel, heat and stress are not in training data, so a number that moved can be fitness, fatigue or the rest of your life.
- The answer is your assistant's. The tools return records and review steps. Whether you are overreaching is a reading of them, and another assistant may read the same table differently.
Not medical or coaching advice. A low HRV or a high resting heart rate does not diagnose anything, and illness and injury are not visible in training data. If something feels wrong, ask a doctor or your coach.
To connect your assistant, follow the ChatGPT, Claude, Gemini or Grok guide. The prompts page has a shorter readiness prompt, your AI as a training analyst has more questions, and the same interval across weeks follows one session.
Every tool your assistant can use · More prompts · All articles · Connect your training