ask_pacebeats
ChatGPTLook up verified facts about PaceBeats features, settings, device connections, sync, workout editing, exports, units, and current limitations. This is product documentation, not athlete data.
explain_session
ChatGPTUse this when the athlete asks why a current/next-week session has its duration, intensity, or place in the week. Prefer a session_ref returned by PaceBeats; otherwise use a date and optional sport. Repeat only recorded rationale and never construct a coaching reason.
get_data_sources
ChatGPTUse this before claiming Garmin, Wahoo or Withings is disconnected, stale, failed, or missing data. Returns redacted connection state, last successful sync, data-through date, and Garmin history-import state. Wahoo supplies recorded activities and cycling workout delivery, not sleep or readiness. Never infer a failure only because a requested date has no reading.
get_plan_overview
ChatGPTUse this for the athlete's full season shape: plan dates, current phase, what phases come next, how many weeks remain, race anchors, and which weeks have sessions built. Use get_week for session-level detail. Numeric training-load targets and planning internals are excluded.
get_races
ChatGPTUse this for what the athlete is training toward, upcoming A/B/C races, race dates and distances, or past race-calendar entries. This is a bounded calendar read, not a race prediction, pacing plan, or result analysis.
get_today
ChatGPTUse this for today's planned training or the next session today. Returns privacy-safe session details, structure, recorded rationale, and week context. Use get_week for another day and never invent advice or hidden metrics.
get_training_history
ChatGPTUse this for what the athlete did recently, whether a past session was completed or missed, and recent sessions by sport. It reads only the last 7, 30, or 90 days. Provider-neutral results exclude training load, heart rate, power, routes, wellness, and raw activity data.
get_training_profile
ChatGPTUse this when the athlete asks what assumptions their plan is using: training focus and goal, weekly hours, recurring day-by-day availability, sport caps, session preferences, and whether strength/fueling equipment is configured. Identity, thresholds, health, body, location, memory, billing, and credentials are excluded.
get_week
ChatGPTUse this for the current or next training week, tomorrow, upcoming key sessions, session counts, and completion status. Use current unless the athlete explicitly asks about next week; use get_today for today specifically.
ask_pacebeats
ClaudeLook up verified facts about PaceBeats features, settings, device connections, sync, workout editing, exports, units, and current limitations. Product documentation only: do not use it for the athlete's own plan or data (use get_today, get_week or get_athlete_setup).
check_readiness
ClaudeUse this when the athlete asks whether to train as planned today, go easy or skip, or how recovered they are for a session. Returns a go, caution or back_off verdict for today's most demanding planned session (or a session_ref from get_today or get_week), fixed-wording reasons, per-signal bands (HRV, resting heart rate, sleep) against the athlete's own 28-day baseline with a trend, a suggested adjustment, and data freshness. It uses the same rule as the morning push. Needs wellness.read; without it, falls back to a load-only verdict with metrics.read, otherwise explains the missing access. Do NOT use it to list or explain sessions (use get_today or get_session), for fitness trends (use get_fitness_form), for illness or injury (use report_disruption to note one), or to change the plan. It never returns raw HRV, sleep, heart-rate or load numbers. It is training guidance, not medical advice; plan changes are confirmed in the PaceBeats app.
get_athlete_setup
ClaudeUse this when the athlete asks how their plan is set up: focus and goal, weekly hours, available days and sports, sport caps, session preferences, strength and fueling equipment, whether Garmin, Wahoo or Withings is connected and last synced, or whether a week is being generated or rebuilt. Pass sections to fetch only profile, availability, connections or generation. Do not use it for what to train (use get_today or get_week), past sessions (use get_training_summary), races (use get_race_outlook), or fitness, thresholds and health (use get_fitness_form or get_thresholds_zones). A connection with no recent reading is not a failure; report the returned state. Identity, contact, thresholds, body, health, location, memory, billing and credentials are never returned.
get_fitness_form
ClaudeUse this for the athlete's fitness and freshness: building or losing fitness, fresh or tired, ramping too fast, recent load in a safe range, and form in 7 and 14 days. Returns a verdict plus labels and bands (fitness trajectory with percent change, fatigue, form zone, weekly ramp, acute:chronic, forecast form zone, data confidence). Do not use it for what to train (use get_today or get_week), hours or distance totals (use get_training_summary), whether to do today's hard session given sleep and recovery (use check_readiness), or zones and thresholds (use get_thresholds_zones). It never returns raw CTL, ATL, TSB, TSS or other load numbers and gives no medical advice. Needs optional metrics.read; without it the result says how to reconnect.
get_plan_outlook
ClaudeUse this for the shape of the coming weeks (up to 16): phases, planned hours per week, a light/moderate/high/peak load label, change versus the prior week, recovery, taper and race weeks, key sessions of built weeks, and how far sessions are built. Good for 'what does my next month look like' or 'when do I taper'. Do not use it for one day or week (use get_today or get_week), why a session exists (use get_session), past training (use get_training_summary), or race predictions and pacing (use get_race_outlook). Hours for unbuilt weeks are estimates. No fitness, wellness or raw load numbers.
get_race_outlook
ClaudeUse this for the athlete's race calendar (A/B/C priority, dates, distances, days to go, whether planned in PaceBeats) and to get a race_ref. Returns upcoming races by default, or past with window=past. Pass a race_ref for one race: on-track verdict, predicted finish range with confidence, per-leg pacing, taper timing and race-phase guidance. Finish range and pacing need optional metrics.read and are not_available without it (verdict, taper and guidance are not). Do not use it for today's or this week's sessions (use get_today or get_week), season phases (use get_plan_outlook), fitness and form (use get_fitness_form), or a finished race's result (use get_race_results with a race_ref from window=past). One race per call; predictions are deterministic estimates, not guarantees.
get_race_results
ClaudeUse this after a race has finished and its result is confirmed in PaceBeats: finish time, swim/bike/run splits and transitions, placing, result vs the pre-race prediction band, which leg beat prediction most, and the saved debrief summary. Without race_ref it lists recent confirmed results; with a race_ref (from get_race_outlook with window=past) it returns that race in detail including the debrief. Do not use it for upcoming races, predictions, pacing or taper (use get_race_outlook), or training sessions (use get_session or get_training_summary). It only reads confirmed results and never confirms one, generates a debrief or recomputes a prediction; a race with no confirmed result returns no_data.
get_session
ClaudeUse this when the athlete asks about ONE session: what it consists of, why it is in the plan, or how a completed one went (planned vs actual, zone split, intervals hit, aerobic drift, reported effort). Requires a session_ref from get_today, get_week, or get_training_summary; never invent one. Do NOT use it to list a day or week (use get_today or get_week), for trends (use get_training_summary), or for fitness, thresholds or readiness (use get_fitness_form, get_thresholds_zones, check_readiness). Results are labels and shares of time; optional metrics.read adds a bands field with zone ranges, otherwise it is not_available. Relay the rationale without inventing numbers or medical advice.
get_strength_session
ClaudeUse this when the athlete asks about a gym session: prescribed lifts, sets and reps, sets already logged, the load used last time, or how one lift has progressed. Pass a strength session_ref (from get_today, get_week, or get_training_summary) for that session, or an exercise name or exercise_ref with optional range_days for that lift's recent top sets and an up, flat or down trend. Loads are the athlete's own logged kilograms and reps. Do NOT use it for swim, bike or run sessions (use get_session), a day or week overview (use get_today or get_week), or totals (use get_training_summary). It cannot log a set (use log_strength_set) or change the plan, and never invents a load: say when nothing is logged.
get_thresholds_zones
ClaudeUse this when the athlete asks for their zones in numbers (bike watts, run and swim pace, heart-rate bands), how fresh they are, whether a retest is due, or whether a suggested threshold update awaits review. Returns zone ranges per sport with the threshold's source, age in days, a stale flag and weeks until retest; pending reviews give only the direction and a label. Do not use it for today's targets or a session's steps (use get_today or get_session), fitness or form (use get_fitness_form), readiness (use check_readiness), or to change a threshold, accept a review or schedule a test (that happens in the PaceBeats app). It never returns the threshold value itself. Needs metrics.read: without it the call returns status unavailable with a reconnect hint, and it is refused under 18 or with no date of birth on file.
get_today
ClaudeUse this when the athlete asks what they are training today, what a session involves (warm-up, main set, reps, zones, RPE), or what was planned or done on a day within 7 days (pass date, YYYY-MM-DD). Returns every session that day with a session_ref, block structure as zone names and RPE, the recorded rationale, week context, whether the week is being rebuilt, and how many plan changes await confirmation in the app. Optional metrics.read adds absolute power, pace and heart-rate targets per block; optional wellness.read adds a readiness verdict (go, caution, back_off). A not_available field names the missing permission; relay it. Do not use it for whole weeks or totals (use get_week), past history, or a deeper readiness answer (use check_readiness). It has no fitness, load or raw wellness numbers and cannot change the plan; plan changes are confirmed in the PaceBeats app.
get_training_summary
ClaudeUse this for training over weeks or months: total hours, distance and sessions, plan completion, volume by week, month or sport, consistency, easy-vs-hard mix, longest sessions, and volume up or down versus the previous period. Covers 4 to 52 weeks and lists up to 25 recent sessions with session_refs. Do not use it for today's or this week's plan (use get_today or get_week), one session (use get_session), fitness or form (use get_fitness_form), or future plans (use get_plan_outlook). Deterministic aggregates only; no load, heart rate, power, wellness or provider data.
get_week
ClaudeUse this for any training week from 8 weeks back to 12 ahead: this week, next week, last week, or a named one (week_offset 0 is this week, 1 next, -1 last). Returns each day's planned sessions with what was done, planned vs actual minutes by sport, a compliance band, key sessions hit or missed, whether load is under, on or over plan, the latest plan change, and the next key session. Do not use it for only today (use get_today), one workout's structure or rationale (use get_session; session_ref is null for sessions more than 14 days ahead), a multi-week look-ahead (use get_plan_outlook), trends (use get_training_summary), or fitness, readiness or injury risk: it reports no load, threshold or wellness numbers.
get_weekly_review
ClaudeUse this when the athlete asks how a past week went: last week or up to 8 weeks back (week_offset -1 is last week; 0 is the week in progress). Returns plan adherence bands, per-session execution (intervals completed, on target, stopped early, aerobic drift) from stored step analysis, what each missed session cost the week, how the plan responded (change note, next week lighter or heavier), and, on plans with weekly insights and optional metrics.read, the stored insight cards; insights_status says why they are missing (tier_locked, not_available, none_stored). Use get_week for the day-by-day schedule of any week including future ones, get_session for one workout, get_training_summary for trends, get_today for today. Do not use it to judge current fitness, readiness or injury risk. It never generates insights or debriefs and returns labels and bands, not load, threshold or wellness numbers.
log_session
ClaudeUse this when the athlete says how a planned session went and wants it recorded: done, partial, how hard it felt (rpe or feel), or a note in their words. Requires a session_ref from get_today, get_week, or get_training_summary; never invent one. This tool STAGES before it saves: call without confirmation_token for a preview of exactly what would be recorded (including any effort or feedback it would replace), get the athlete's agreement, then call again with the same fields plus the confirmation_token (valid 5 minutes, only for those fields). Staging leaves the workout unchanged but records an audit event. A done session counts the plan's duration and load like Mark done in the app; if a synced activity exists only effort and note are saved and its recorded load never changes. A partial saves only how it felt. Skipped sessions cannot be recorded here. Do NOT use it to change, move, shorten or skip a session (use propose_plan_change), report illness or injury (use report_disruption), log strength sets (use log_strength_set), or read a session (use get_session). It never confirms a plan change; plan changes are confirmed only in the PaceBeats app. Relay status and next_step; claim a save only when status is logged or feel_only.
log_strength_set
ClaudeUse this when the athlete states a set they just did in a planned gym session, e.g. 'squat set 2 was 80 kg for 6'. Pass session_ref and exercise_ref from get_strength_session, the set number from 1, reps and, for a loaded lift, weight_kg. It stages before it commits: the first call (no confirmation_token) leaves the set unchanged but records an audit event, shows the set and anything it would replace, and returns a confirmation_token valid a few minutes. Read the set back and, once the athlete agrees, call again with the same values and token. Saving the same set twice changes nothing; logging the last prescribed set completes the session. Do NOT use it to record a whole session as done, skipped or partial (use log_session), to look up prescribed or logged sets (use get_strength_session), for swim, bike or run work, to change the plan (use propose_plan_change), or to delete a set. Needs plan.log; unavailable under 18. Plan changes are confirmed only in the PaceBeats app. Never guess a load or reps the athlete did not state.
propose_plan_change
ClaudeUse this when the athlete asks to change ONE thing: move a session to another day, shorten or lengthen it (to_minutes), skip it, make it easy (swap_easy), or make a week easier (easier_week, optional reduce_percent 5 to 25). It only STAGES a proposal: nothing changes until the athlete confirms it in the PaceBeats app; this tool cannot confirm, apply or undo anything, so never say a change is made. Give them the returned summary and confirm_options.in_app_url link, and mention the expiry. Needs a session_ref from get_today or get_week (never invent one) for every kind except easier_week; only this week and next, only sessions not yet done. Repeating the same change returns the pending one. Do NOT use it for pain, illness or injury (use report_disruption), to log a done workout (use log_session), to regenerate a week, start or end a protected mode, or change races, thresholds, availability or preferences, or to read the plan or why it changed (use get_week, get_session or what_changed). If it says not_proposed, relay the reason and point them to the app; do not retry with a workaround.
report_disruption
ClaudeUse this when the athlete says something is getting in the way of training: ill, injured, travelling, or heavily fatigued. It saves a short note that expires (7 to 28 days), can stage an easier week for review, and points to constraint mode in the app. Two steps: the first call, without confirmation_token, only previews the note and optional proposal and records an audit event; show what will be saved and ask. If they agree, call again with the same fields and the confirmation_token. kind is illness, injury, travel or fatigue. athlete_words is optional, a short phrase the athlete actually said; do not invent detail. Set ease_plan true only if they asked to lighten the week. Nothing here changes the training plan: an easier week is only proposed, and the athlete confirms it in the PaceBeats app. It never starts or ends constraint mode, rebuilds a week, or deletes anything. Do NOT use it for a single missed or shortened session (use log_session), to move, shorten or swap a session (use propose_plan_change), to ask whether to train today (use check_readiness), or for medical questions. It is not medical advice; for severe pain or feeling unwell, tell the athlete to see a clinician. Free accounts get the note only.
what_changed
ClaudeUse this when the athlete asks why their plan looks different, what PaceBeats or their coach changed recently, whether a session was moved, shortened, swapped or a week rebuilt, who did it and why, or what suggested changes still await their decision (before/after and expiry). Also reports whether structured planning is paused and whether a constraint mode (injury, travel, recovery) is shaping the plan. Reasons are fixed plain-language text, not the coach's private notes. Do not use it to see the plan itself (use get_today, get_week or get_plan_outlook), how a session went (use get_session), or to change, confirm or dismiss anything: proposals are confirmed only in the PaceBeats app and this tool never applies a change.