Vertical

Retrieve the athlete's actual logged activities with their REAL distance, duration, average pace, and average/max heart rate for each. Use for any question about a specific past activity or training history (e.g. "what was my pace on Saturday's race", "how far was my long run", "have I ever run 30k"). Filter by date range and/or sport. Returns grounded figures — quote them via their [fact:ID] tokens.

getActivities

Retrieve the per-lap / per-interval splits (pace, average HR, max HR, distance for EACH lap) of the activity on a given date, returned as grounded [fact:ID] tokens. Laps are numbered in order — early warm-up laps are slower/easier than work intervals, so read the per-lap pace before calling a lap a "rep". If the athlete identifies the active/work laps, pass those 1-indexed lap numbers in activeLapNumbers; that selection is authoritative for the active-rep analysis even when it differs from the planned workout.

getActivitySplits

The athlete's current coaching snapshot: profile, active plan (goal races, current phase/week), training load (CTL fitness / ATL fatigue / TSB form), physiological thresholds, recovery readiness, plan health, and active injuries. Call this first to ground advice in the athlete's current state.

getAthleteOverview

Retrieve the full season arc: goals, phases, timeline events, week-by-week budgets, and logged workouts. Use for any season question beyond the always-on summary.

getSeasonDetail

Retrieve the athlete's training load and weekly volume: current fitness (CTL), fatigue (ATL), form (TSB), weekly CTL ramp, and week-by-week distance + hours DONE vs PLANNED, filterable by date range and/or sport. Each figure is a [fact:ID] token — quote it verbatim. Weeks flagged "(in progress)" are not yet complete.

getTrainingLoad

Read whether Vertical is currently pushing scheduled workouts to the athlete's connected device (Garmin/COROS). Returns the current on/off state.

getWorkoutPushSetting

Report whether the athlete's upcoming planned workouts have actually synced to their connected device (Garmin/COROS). Returns per-device counts of synced/pending/failed workouts plus details of any failures. Use this to answer "did my workouts reach my watch?".

getWorkoutSyncStatus

Retrieve the athlete's training zones as Easy/Moderate/Hard boundaries (heart-rate by default; pass metric:"pace" or "power" for those). Pass a startDate to ALSO get how much time was spent in each HR zone over that window (e.g. "was last week mostly easy?"). Use for "what are my HR zones", "what pace is zone 2", "how much easy vs hard did I do". Each figure is a [fact:ID] token — quote it verbatim.

getZones

READ-ONLY what-if projection of a proposed schedule rearrangement (day shift, day move, or swap). Returns the projected day→session mapping with weekday names, every session move (from day X to day Y), and deterministic implications (rest days lost, stacked days, hard-session spacing, sessions landing in the past). Nothing is modified — use it to discuss a hypothetical layout accurately before the athlete decides.

projectWeekShift

Answer natural language questions about training data using SQL analytics. Covers: activities, heart rate, sleep, HRV, stress, training zones, scheduled workouts, feedback ratings/RPE, training load, fitness metrics, menstrual cycle data, and all quantitative training data. Returns structured data that you should interpret in context of the conversation.

queryAnalytics