batch_create_activities
ChatGPTCreate up to 100 activities in a single call. Same per-activity shape and rules as create_activity (notably: distance is in meters, duration in seconds, always set load on planned workouts or they will not appear in training-load or get_training_status's projection, pace step targets are seconds-per-km including for swims spoken in per-100m, and rest days are skipped rather than created). Importing a training plan is the common case: omit its rest days from the array entirely. After importing, call get_training_status with no from/to and read series plus projection — that is the week’s shape and its peak. Do not pass a long history range for this check. SWIM STEPS: the watch reads swimDrill, swimEquipment and swimStroke, never displayName. Set swimDrill on every drill ('drill'), kick ('kick') and pull ('pull') step, which keeps its normal stepType (usually 'interval'; 'drill' is never a stepType), swimEquipment to the one piece of kit that step uses, and swimStroke on every step whose stroke is named. When the athlete names their pool ("50m pool", "25 yard pool"), set poolLength.
batch_delete_activities
ChatGPTDelete up to 100 activities in a single call.
batch_update_activities
ChatGPTUpdate up to 100 activities in a single call. Each entry must include its id.
connect_device
ChatGPTConnect a device to this Shape account from the chat. Returns, per device, whether it is already connected and otherwise a link the athlete opens: for Garmin and Wahoo a one-time sign-in link that works in any browser for 15 minutes and starts the import as soon as they allow Shape; for Apple Health the iPhone app, since Health only connects from the phone. Pass provider when the athlete named their device. Leave it out to get every option with its link, and let them pick. Call it when a tool answered that nothing is synced yet or no device is connected, or when the athlete asks to connect, add or check a watch. Already-connected devices come back with connected: true and no link. Give the athlete the link itself (it is personal and expires), then ask them to come back and ask again once they have allowed Shape.
create_activity
ChatGPTCreate a new planned or completed workout activity for the authenticated user. Top-level distance is in METERS (8 km = 8000, a marathon = 42195) and duration is in SECONDS (45 min = 2700) — convert from whatever units the user speaks in. Always set load on planned workouts: without it the session is invisible to fitness, fatigue and get_training_status's projection. Estimate as (duration_seconds / 3600) × effort² × 100, where effort is 0.25 recovery, 0.5 easy, 0.75 tempo, 1.0 threshold, 1.25 VO2, 1.5 race (a 60-minute easy run is ~25). After creating or moving planned work, call get_training_status with no from/to and read series (the next week of load) and projection (its peak). Do not pass a long from/to for this. Above 1.5 is High. For structured interval workouts, set target to "steps" and provide steps. Write a set of N reps as ONE repeat step (stepType "repeat", numberOfIterations N, workoutSteps = the rep and its recovery), never as N copies written out: copies drift, and "6x400m" comes back as seven. Pace step targets (targetValueOne/Two) MUST be seconds-per-km (240 = 4:00/km; smaller = faster), never min/km strings or meters-per-second, or pace will not export to the user's watch. This includes SWIMMING, which athletes speak in per-100m: convert it, so "2:00 per 100m" is 1200, never 120. Do not create an activity for a rest day: rest is the absence of a workout, and a "Rest Day" row typed as a run with zero distance clutters the calendar and the training log. Skip those days entirely. date is the calendar day (YYYY-MM-DD) and never a timestamp; put time of day in startTime as local HH:mm, since Shape stores no timezone and a UTC instant cannot say what "7am" meant to the athlete. SWIM STEPS: the watch reads swimDrill, swimEquipment and swimStroke, never displayName. Set swimDrill on every drill ('drill'), kick ('kick') and pull ('pull') step, which keeps its normal stepType (usually 'interval'; 'drill' is never a stepType), swimEquipment to the one piece of kit that step uses, and swimStroke on every step whose stroke is named. When the athlete names their pool ("50m pool", "25 yard pool"), set poolLength.
delete_activity
ChatGPTDelete an activity. Unlinks any paired counterpart.
get_activity
ChatGPTFetch a single Shape activity by id. If this is a completed workout with plannedActivityId set, that id is the plan — fetch it for the planned description and steps; they are not copied onto the completed row. The recorded route is left out unless you ask for it, and get_activity_details is the better way to get it: it serves GPS as lat/lng channels at a resolution you pick, where map is an opaque encoded polyline only a map renderer can use.
get_activity_details
ChatGPTFetch the recorded time-series for one completed activity: heart rate, pace/speed, cadence, power, elevation, GPS and timestamps, running dynamics and pedal balance when the device recorded them, plus lap splits, time in each training zone (Shape's model, and the device's own zones when it recorded them) and a pool swim's lengths. Use this for questions the summary can't answer — how the effort was paced, where the athlete faded, how hard each interval was. Channels are parallel arrays indexed against time (seconds since the activity start), units names the unit of each, and resolutionSeconds is the spacing between points — raise points (up to 2000) if it's too coarse. laps and zones are computed from the full recording before any reduction, so they stay exact whatever resolution you ask for. Only activities recorded by a connected device have this. When there is none, the 404 carries a reason code (not_completed, manual_entry, source_unsupported, imported_before_streams, no_samples_recorded) and a message written to be relayed to the user as-is — use it rather than guessing why the data is absent. Prefer the laps and zones summaries over reading the raw arrays when they answer the question. When a workout was imported from two connected sources, the richest recording is served and detailFrom names it — so source here may differ from the activity's own source.
get_help
ChatGPTShape's help center: connecting a watch or health app, a missing workout or sync, sending workouts to a watch or calendar, connecting Claude or ChatGPT, training load, plans and billing. Use it when the athlete has a problem with Shape itself or asks how to do something in it, before you guess at steps or settings: call it without article for the list of articles, each with one line on what it covers, then call it with the matching slug to read that article. Answer from the article in your own words, only the steps that fit their situation, and give its link. The answer says what to do if the steps don't solve it. Not for training questions, which you answer yourself.
get_profile
ChatGPTThe athlete's numbers that score training load and set heart-rate and pace zones: max, resting and threshold heart rate, cycling FTP, running threshold pace (seconds per km) and swim threshold (seconds per 100 m). Each comes with where it is from (set by the athlete, from the device, from Apple Health, from the daily readings) and since when. A null value means nothing is on file: sessions that need it get no training load, which is why load or fitness can read as zero. Also the profile fields that shape a plan: gender, birth year, the distance unit Shape shows (km or mi), the day the week starts on, and the pool swims are written for. And connections: the devices connected to the account (Garmin, Wahoo, Apple Health) with when each was connected, empty when nothing is connected yet; connect_device adds one.
get_training_status
ChatGPTHow the athlete is doing right now: readiness (are they recovered enough to train hard), training load (fitness, fatigue, form and the acute:chronic ratio), and what their planned workouts do to that ratio over the next week. Call this for 'should I train hard today', 'am I overtraining', 'how is my fitness trending' or 'why is my readiness low' — it answers all four in one call, and every readiness score reports the drivers that produced it so the number can be explained rather than just asserted. Also call this BEFORE planning a block and AFTER creating or rearranging planned workouts: omit from and to. The snapshot already includes series for today plus the next 7 days of fitness/fatigue/form/ratio (no readiness — that cannot be projected) and projection (the peak ratio in that week). It is null when nothing planned has a load. A ratio above 1.5 is High. Pass from and to together only when the question is a trend over time. A year of history is tens of thousands of tokens; the default week is not. Two readiness numbers, deliberately: the snapshot includes training already completed today and so falls through the day, while every day in series is MORNING readiness and never includes it. A past day's series score is how they woke up, not how the day ended, so the snapshot and the last series element can differ for the same date. Each reports which it is in basis. For what is actually on the calendar today, call list_activities — this returns the plan's consequence, not the plan.
list_activities
ChatGPTList the authenticated user's activities (planned and completed workouts), newest first. Filter by date range, sport type and completed state. A fulfilled plan is returned once, as the completed workout — its description and steps are not the plan. To read the plan (title, description, structured steps), call get_activity with plannedActivityId, or set includePaired=true to also return the planned row. Do not treat the completed row's description as the prescription. Summary fields only: routes never come back here, and the recorded time-series comes from get_activity_details one activity at a time.
list_health_metrics
ChatGPTList the authenticated user's daily health metrics (sleep, HRV, resting HR, body battery, VO2max, body composition, blood pressure, steps, etc.), merged across Garmin and Apple into one record per day. Supports from/to date filters, an optional single source, and a metrics whitelist. The metrics values are exact field ids, enumerated in this tool's input schema — restingHR, hrvMs, sleepDurationSec, sleepScore, bodyBatteryCharged, vo2max and so on — not prose names like restingHeartRate or sleepDuration. Omit metrics entirely to get everything recorded that day, which is the right default when you don't know what the user has. Each value reports which source it came from. When from is omitted, only the last 90 days are returned; pass from to reach further back.
pair_activities
ChatGPTPair a completed activity with the planned activity it fulfills. Both must belong to the user.
send_feedback
ChatGPTSend a message from the athlete to the Shape team: a bug, a missing feature, or something that did not work the way they expected. A person reads it and replies by email. Call this only when the athlete explicitly asks to send feedback, report a problem or contact Shape. Never call it on your own: not after a tool error, not because they sound unhappy, and not to report your own difficulties. If it would help them, offer once and wait for their yes. Show them the message and send it after they agree. Say what they were trying to do and what happened, in their words. Leave out workouts, health data and readings unless they ask to include them; their account and the app they are using are attached for you. Send it once: success means it was delivered. Not for training questions, which you answer yourself.
unpair_activity
ChatGPTRemove the pairing between a planned and completed activity.
update_activity
ChatGPTUpdate fields on an existing activity. Provide the id and any subset of fields to change. If you change duration or intensity on a planned workout, recompute load with (duration_seconds / 3600) × effort² × 100 and then call get_training_status to see the new projection. SWIM STEPS: the watch reads swimDrill, swimEquipment and swimStroke, never displayName. Set swimDrill on every drill ('drill'), kick ('kick') and pull ('pull') step, which keeps its normal stepType (usually 'interval'; 'drill' is never a stepType), swimEquipment to the one piece of kit that step uses, and swimStroke on every step whose stroke is named. When the athlete names their pool ("50m pool", "25 yard pool"), set poolLength.
update_profile
ChatGPTSave numbers the athlete gave you: max, resting or threshold heart rate (bpm), cycling FTP (W), running threshold pace (seconds per km, 5:00/km is 300) or swim threshold (seconds per 100 m). Pass only the fields they named, as whole numbers; a value outside the settings ranges is refused. Each is saved as the athlete's own value from today, exactly as typing it in Shape's settings does, and outranks what a device reports. Load follows the same rule as settings: a first value scores the sessions that had no load (load: "filled"); a changed value applies from today and older sessions keep their load (load: "from_today"). Also saves gender (male or female, an input to heart-rate load under the same rule), birth year, distance unit (km or mi), the first day of the week (monday or sunday) and pool length. Only save what the athlete actually stated or confirmed. Never guess a value, never estimate a heart rate from their age, and never save one they did not agree to. null hands a number back to the device's value, or clears gender or birth year.