Every IcuSync Tool, Explained

IcuSync gives Claude 18 tools to work with your Intervals.icu data. This page covers the 12 read tools, the ones Claude uses to understand your training. Each one below explains what it returns, why it matters, and a sample prompt to try.

This page reflects the tool set as of 26 August 2026. New tools get added regularly, check the changelog for the latest.

We've grouped them by what you're actually trying to find out, not alphabetically.

Who you are

get_athlete_profile

This is the first thing Claude checks in most conversations. It returns your training zones, thresholds (FTP, threshold pace, LTHR), and sport settings for each discipline you've set up in Intervals.icu.

Claude also validates this data automatically. If your FTP looks stale compared to recent power numbers, or a zone is missing for a sport you're active in, Claude will flag it before giving you analysis that depends on it.

Try asking: "What are my current training zones?"

What you've done

get_training_history

A list of your recent activities: sport, duration, distance, load, and the gear and tags attached to each one. This is usually the starting point for any question about a block of training rather than a single session.

Try asking: "What did my training look like over the last two weeks?"

get_activity_detail

The full breakdown of one specific activity: interval-by-interval pace, power, and HR, exact distance splits (independent of how your device auto-lapped it), and weather conditions if they were recorded. Splits are computed straight from the GPS or distance stream, so they're accurate even when a workout's auto-detected segments don't land on clean km or mile boundaries.

Try asking: "Break down my splits from yesterday's tempo run."

get_extended_metrics

Sensor data most apps don't surface clearly: core temperature, DFA alpha-1, W' balance depletion, blood glucose for cyclists, ground contact time and vertical oscillation for runners. Also includes any custom Activity Fields you've set up (lactate, RPE, pain scores).

For W' balance specifically, Claude can see not just the average but how low your reserve actually dropped and how long you spent deeply depleted, which is the difference between a ride that never troubled your matches and one that burned through them despite a similar average power.

Availability depends on your device and sensors.

Try asking: "How did my ground contact time and vertical oscillation look in yesterday's run?"

Where you're at

get_fitness

Your CTL (fitness), ATL (fatigue), and TSB (form) across any date range. Claude checks this automatically before recommending a training plan, so workouts reflect your actual recovery state rather than an assumed baseline.

Try asking: "How's my form looking heading into this weekend's race?"

get_training_summary

Aggregated stats over a date range: total volume, TSS, and calories by sport, time in each power/HR/pace zone, and a week-by-week breakdown. This is the tool for block reviews rather than single-session detail.

Try asking: "How much Zone 2 have I done this month?"

How you're recovering

get_wellness

Daily sleep, HRV, resting heart rate, body weight, and nutrition (kcal, carbs, protein, fat if you log food in Intervals.icu). Anything device-synced comes through automatically; subjective scores only appear if you or your watch log them.

Try asking: "Has my HRV trended down this week?"

What's coming up

get_events

Your planned calendar: upcoming workouts, races, and any notes attached to them, including fueling targets (carbs per hour) and planned load if you've set those.

Try asking: "What's on my calendar for next week?"

How strong you are

get_best_efforts

Your personal bests across standard distances and durations, pulled directly from Intervals.icu.

Try asking: "What's my 10K PB this year?"

get_power_curves

Your best power output across key durations, plus CP and FTP model estimates, for run and ride. Also supports durability curves, your power after a set amount of accumulated work (e.g. after 1000 kJ), so you can see how you hold power in a fatigued state rather than fresh. Durability thresholds need to be set on your Intervals.icu power curve chart first.

Try asking: "Has my 20-minute power improved this block?"

Advanced analysis

These two are more specialised. Useful if you want to go deeper on climbing or technical terrain, skip them if you just want the basics. Climb segments work across sports, ride power patterns is cycling-specific.

get_climb_segments

Detects sustained climbs in an activity and calculates VAM (vertical ascent in meters per hour) for each one, along with grade and average power if you have a power meter. Works for rides, runs, hikes, and walks. Handles climbs with a brief flat or downhill "shelf" partway up by bridging them into one segment instead of splitting the climb into pieces.

Try asking: "Which climb on today's run or ride had the best VAM?"

get_ride_power_patterns

For technical or rolling rides where average power and zone time hide what's actually happening. Splits coasting time into short coasts (a breather between pedal strokes on a technical section) and long coasts (a real descent or stop), and detects repeated hard/easy burst patterns, the on-off surges typical of MTB, cyclocross, gravel, or criterium racing. A ride can look unremarkable on average power alone while actually being a string of repeated efforts, this tool is what shows that.

Requires a power meter, ride activities only.

Try asking: "Was that gravel ride actually steady, or a lot of surging?"

None of these need setup on your end. Claude calls the right tool automatically based on what you ask, you don't need to know the tool names above to use them, they're here so you know what's possible.

IcuSync has 18 tools in total. This page covers the 12 read tools above. The other 6 write data back to Intervals.icu, pushing, editing, and deleting workouts, logging wellness data, updating completed activities, and writing threshold values, and are covered elsewhere.

Want more examples? See Prompts & Charts for a bigger collection of prompts to try.