I have now made a further change to getonedayfullactivity tool to reduce the overhead when a large number for intervals was present in a single activity, and the size returned to ChatGPT would exceed its limits, whilst this is an unusual case, the new changes also mean a faster response and faster render times. There should be no loss of function in an activity analysis. All intervals are preserved and it still supports multi-sport and those with CORE heat sensors.
As a reminder you can ask ChatGPT what tools are available show tools available and it will provide a full list.
# REPORTS
## Weekly Report
runWeeklyReportV2(
test?: string,
lite?: boolean,
start?: string, # YYYY-MM-DD
athleteID?: string
)
## Season Report
runSeasonReportV2(
lite?: boolean,
athleteID?: string
)
## Wellness Report
runWellnessReportV2(
athleteID?: string
)
## Summary Report
runSummaryReportV2(
start?: string, # YYYY-MM-DD
end?: string, # YYYY-MM-DD
athleteID?: string
)
# CALENDAR
## Read Calendar
readCalendarV1(
start: string, # ISO date
end: string, # ISO date
lite?: boolean,
athleteID?: string
)
## Write Calendar (Create / Update Workouts)
writeCalendarV1(
planned_workouts: [
{
date: string, # YYYY-MM-DD
title: string,
type: string, # Run | Ride | Swim | etc.
category: string, # WORKOUT | RACE_A | NOTE | etc.
description: string, # STRICT interval format (- lines only)
duration_minutes: number,
tss?: number,
carbs_per_hour?: number
}
]
)
## Delete Calendar
deleteCalendarV1(
id?: any,
date?: string,
dates?: string[]
)
# ACTIVITY
## Full Activity (by date or id)
getOneDayFullActivityV1(
date?: string, # YYYY-MM-DD
activity_id?: string,
athleteID?: string
)
## List Activities (Light)
listActivitiesLight(
oldest?: string,
newest?: string,
fields?: string, # comma-separated (note if not specified a default set is applied)
athleteID?: string
)
# WELLNESS
## One Day Wellness
getOneDayWellnessV1(
date: string, # YYYY-MM-DD
athleteID?: string
)
# PERFORMANCE MODELS
## Power Curves
getPowerCurvesExtV1(
type: "Ride" | "Run" | "Swim",
curves?: string,
pmType?: "MS_2P" | "MORTON_3P" | "FFT_CURVES" | "ECP",
athleteID?: string
)
## Pace Curves
getPaceCurvesExtV1(
type: "Run" | "Swim",
curves?: string,
athleteID?: string
)
## HR Curves
getHRCurvesV1(
curves?: string,
type?: "Ride" | "Run" | "Swim",
athleteID?: string
)
## Power-HR Curve
getPowerHRCurveV1(
start: string, # YYYY-MM-DD
end: string, # YYYY-MM-DD
athleteID?: string
)
## MMP Model
getMMPModelV1(
type?: "Ride" | "Run" | "Swim",
athleteID?: string
)
# ATHLETE / DATA
## Training Plan
getAthleteTrainingPlanV1(
athleteID?: string
)
## Athlete Profile
getAthleteProfileV1(
athleteID?: string
)
## Sport Settings
getSportSettingsV1(
athleteID?: string
)
## Coached Athletes
getCoachedAthletesV1()
# COMMUNICATION
## Send Message
sendChatMessageV1(
content: string,
chat_id?: string,
to_athlete_id?: string,
to_activity_id?: string
)
# DATA QUALITY
## Data Quality Report
runDataQualityReportV1(
athleteID?: string
)
Br and a great Easter break all 
Clive
VO2 (30s ~360W)
Large repeated depletion (down to ~5–7 kJ)
Recovery (30s ~178W)
Partial recharge (never full)
Z2 (~160W)
Mostly restored / stable
Updated Strategy (Given Weather + Bank Holiday)
Yes — you can extend today
Two Smart Options
Option A — “Make Today the Big Day” (Recommended)
Skip or downgrade Monday VO2
Option B — “Keep Structure, Just Add a Bit”
What NOT to do
Coaching Insight
My Recommendation (Clear Call)
Summary (Key Changes)