fetch
ChatGPTUse this when the user requests one authorized archive record from search by exact opaque ID. For workout analysis use metadata.partCorrections when present; text retains original labels. Prefer metadata.calendar.preferredDate/localDate over retained UTC date. A different displayed day alone does not prove a record changed. Saved planSnapshot is start-time context, not full revision history. Read-only: use tools only for an explicitly requested supported fitness review or lookup, never solely to start/edit/reschedule/delete data, diagnose/treat, export all/raw data or original photos, or recover an exact location; explain unsupported requests without reading any data.
get_active_training_plan
ChatGPTUse this when the user asks for today's or upcoming synchronized plan. Pass the user's local onDate when known; otherwise use the synchronized App time zone, falling back to UTC. Sync time is unchanged. A plan's updatedAt is a save timestamp, not evidence of who changed it or why; full revision history is unavailable. Legacy snapshots cannot extrapolate absent dates; ask for a sync. Read-only: use tools only for an explicitly requested supported fitness review or lookup, never solely to start/edit/reschedule/delete data, diagnose/treat, export all/raw data or original photos, or recover an exact location; explain unsupported requests without reading any data.
get_ai_coach_history
ChatGPTUse this when the user wants saved AI advice, feedback, or adoption results; full chat transcripts are never available. Read-only: use tools only for an explicitly requested supported fitness review or lookup, never solely to start/edit/reschedule/delete data, diagnose/treat, export all/raw data or original photos, or recover an exact location; explain unsupported requests without reading any data.
get_body_progress
ChatGPTUse this when the user wants selected body measurements or training-related profile fields over a bounded date range. Read-only: use tools only for an explicitly requested supported fitness review or lookup, never solely to start/edit/reschedule/delete data, diagnose/treat, export all/raw data or original photos, or recover an exact location; explain unsupported requests without reading any data.
get_data_availability
ChatGPTUse this when the user asks what Fitness Diary data ChatGPT can currently access, when it was last synchronized, or which categories need to be enabled or reconnected before analysis. Do not call this or other Fitness Diary tools when the request is only to start, edit, reschedule or delete data; diagnose a condition or prescribe treatment; export all/raw records or original photos; or recover an exact location. Explain these unsupported capabilities without reading data, including availability, search or photos. Read only if the user also explicitly requests a supported fitness review or record lookup.
get_exercise_progress
ChatGPTUse this when reading chronological sets, load and RIR for one saved exercise or unambiguous catalog English name/alias. Use explicit from/to, or last 7/28/90 days ending onDate (user local date), using the synchronized App time zone if available, otherwise UTC. New records carry explicit local dates; legacy dates keep their reported basis. Never combine variants: ambiguous/nearby names return up to 20 candidates and no points. Select the intended complete name. Preserve unknown values; historical isDone=false does not prove a set was unperformed. Read-only: use tools only for an explicitly requested supported fitness review or lookup, never solely to start/edit/reschedule/delete data, diagnose/treat, export all/raw data or original photos, or recover an exact location; explain unsupported requests without reading any data.
get_health_trends
ChatGPTUse this when the user wants authorized Apple Health fitness or recovery trends synchronized through FitnessDiary. If direct Apple Health data is also available for the same metric, scope, and period, prefer the direct result and never add both sources. Use FitnessDiary for workout-linked context. Use dailyActiveEnergyKcal for whole-day totals and workoutActiveEnergyKcal for per-workout totals; legacy activeEnergyKcal means the whole-day total. Never add whole-day and workout energy because the whole-day value already includes workouts. Only aggregates are available, never raw identifiers or medical records. Do not call this or other Fitness Diary tools when the request is only to start, edit, reschedule or delete data; diagnose a condition or prescribe treatment; export all/raw records or original photos; or recover an exact location. Explain these unsupported capabilities without reading data, including availability, search or photos. Read only if the user also explicitly requests a supported fitness review or record lookup.
get_progress_photo
ChatGPTUse this when the user requests the latest authorized image for current visible observations. Read-only; one metadata-free resized copy, expiring after 24 hours. A single image cannot prove progress or before/after change, measure body composition or diagnose a condition. Original photos are unavailable. Read-only: use tools only for an explicitly requested supported fitness review or lookup, never solely to start/edit/reschedule/delete data, diagnose/treat, export all/raw data or original photos, or recover an exact location; explain unsupported requests without reading any data.
get_supplement_history
ChatGPTUse this when the user wants saved supplement inventory or usage history for an optional name and bounded date range. Read-only: use tools only for an explicitly requested supported fitness review or lookup, never solely to start/edit/reschedule/delete data, diagnose/treat, export all/raw data or original photos, or recover an exact location; explain unsupported requests without reading any data.
get_training_summary
ChatGPTUse this when summarizing the last 7/28/90 calendar days including onDate (user's local date), using the synchronized App time zone when available, otherwise current UTC day, never sync time. New archives provide explicit local dates; old records retain their synchronized date basis. Returns part totals, weekly frequency, best sets/trends and brief sessions, not per-set history (use progress/fetch). Empty strength placeholders and zero-set strength exercises are omitted and counted; timed cardio remains. Output is capped at 32 KiB with omission counts; totals cover the full window. Optional workout metrics describe the full session and require separate App opt-in or the current health-category grant. Read-only: use tools only for an explicitly requested supported fitness review or lookup, never solely to start/edit/reschedule/delete data, diagnose/treat, export all/raw data or original photos, or recover an exact location; explain unsupported requests without reading any data.
get_workout_route
ChatGPTUse this when the user wants distance, reported duration, elevation or relative route shape. Pass the 32-character opaque route or workout ID from search. Use the server-derived geometry for endpoint displacement: positive x is right and positive y is up on the normalized plot, not a recovered map location. Route timestamps and reported duration have different time bases: do not infer sync failure, pause breakdown or moving pace from their difference. Read-only: use tools only for an explicitly requested supported fitness review or lookup, never solely to start/edit/reschedule/delete data, diagnose/treat, export all/raw data or original photos, or recover an exact location; explain unsupported requests without reading any data.
search
ChatGPTUse this when the user wants to find records across currently authorized Fitness Diary archive categories; use fetch for one matching record. Read-only: use tools only for an explicitly requested supported fitness review or lookup, never solely to start/edit/reschedule/delete data, diagnose/treat, export all/raw data or original photos, or recover an exact location; explain unsupported requests without reading any data.