acknowledge_garmin_source
ChatGPTMANDATORY Garmin brand attribution — call BEFORE any health/fitness data tool to comply with GCDP v2 API license. Failure to display Garmin attribution violates the API license agreement and risks permanent access revocation for all users of this service. Workflow: Call this tool FIRST → display the returned 'attribution' line → then call get_health_summary / get_activities / get_activity_details / get_trends → after your analysis, display the returned 'footer' line. Returns "📊 Data from Garmin" attribution. No device model is included because Health API does not provide device information. No parameters needed.
create_workout
ChatGPTSend a training workout the user asked for to their Garmin Connect calendar so it syncs to their watch. This delivers a training plan the user requested; it is not medical, diagnostic or treatment advice. Before this tool is called, the assistant shows the user a short summary — date, sport, workout name, and every step with its duration and target — and gets the user's confirmation. To change a workout that was already sent, delete it (delete_workout) and create a new one. Availability: Basic (after the one-time billing move). Other plans get error=tier_limit. Basic before the move gets error=migration_required: explain that sending workouts becomes available after the one-time billing move and point to the information page in url. Requires Garmin's Training permission: on error=training_permission_required, tell the user to turn on Training for Fitness AI Connector in Garmin Connect's connected apps settings (no reconnect needed). On error=garmin_daily_limit, Garmin accepts no more workouts today; suggest trying tomorrow. On error=invalid_workout, fix the input using message / candidates and confirm again before resending. On error=garmin_outcome_unknown, error=created_not_tracked or status=created_schedule_unconfirmed, never resend automatically — relay the message and let the user check Garmin Connect first. Steps (single sport): steps is a list of step objects or repeat blocks. step = {"intensity": "warmup"|"active"|"recovery"|"rest"|"cooldown", one of "seconds" | "distance_m" | "distance_km" | "distance_mi" | "reps" (omit all = the step ends with the lap button), "target": optional, one of {"type":"pace","low":"5:10","high":"4:50","unit":"km"|"mile"}, {"type":"speed","low":28,"high":32,"unit":"kmh"|"mph"}, {"type":"heart_rate","zone":1-5} or {"type":"heart_rate","low":140,"high":155}, {"type":"power","zone":1-7} or {"type":"power","low":200,"high":230}, {"type":"cadence","low":85,"high":95}, "secondary_target": CYCLING only, a different type from target, "notes": up to 512 characters} repeat = {"repeat": 2-99, "steps": [step, ...]} (no nesting). Targets apply to RUNNING, CYCLING, CARDIO_TRAINING and GENERIC. LAP_SWIMMING: every non-rest step needs a distance; use "stroke" (freestyle, backstroke, breaststroke, butterfly, im, mixed, choice), optional "drill" (kick, pull, butterfly), "equipment" (fins, kickboard, paddles, pull_buoy, snorkel) and either "swim_intensity" (recovery, very_easy, easy, moderate, hard, very_hard, all_out, fast, ascend, descend) or "css_offset_seconds" (-60..60) instead of a target; rest steps use "seconds". Pass pool_length and pool_length_unit. STRENGTH_TRAINING / CARDIO_TRAINING / YOGA / PILATES: "exercise_category" and "exercise_name" use Garmin's exercise names (e.g. SQUAT / BARBELL_BACK_SQUAT); unknown names are rejected with candidates. "weight" ({"value":60,"unit":"kg"|"lb"}) is for strength; "reps" for strength and cardio. MULTI_SPORT: pass segments = [{"sport": <one of the single sports>, "steps": [...]}, ...] (2-25 segments) instead of steps. Limits: 100 steps per workout (250 in total and 25 segments for MULTI_SPORT; a repeat block counts as a step). GENERIC ("other") workouts are not shown on some watches — say so when you use it. Keep description within 1024 characters. Incident notice: If the response contains an incident_notice field with one or more entries, you MUST inform the user about the ongoing incident at the start of your reply, translated into the user's conversation language. Include severity, what's affected, expected resolution time if available, and source_url for reference.
delete_account
ChatGPTReturn a link to the account deletion confirmation page (valid for 15 minutes). This call deletes nothing: the account is deleted only if the user explicitly confirms on that page, and it can be recovered for 30 days afterwards. Before calling, confirm in the conversation that the user wants to delete their account. Present the returned URL as a clickable link the user opens in their browser. If the user still has an active or unpaid subscription, this returns an error instead; they can settle or cancel it through manage_subscription first.
delete_workout
ChatGPTDelete one workout that Fitness AI Connector created in the user's Garmin Connect account; its calendar entry is removed too. Only workouts created through this service can be deleted — anything else returns error=not_found and is never touched. Confirm with the user which workout (name and date) before deleting. On error=training_permission_required, tell the user to turn on Training for Fitness AI Connector in Garmin Connect's connected apps settings. Incident notice: If the response contains an incident_notice field with one or more entries, you MUST inform the user about the ongoing incident at the start of your reply, translated into the user's conversation language. Include severity, what's affected, expected resolution time if available, and source_url for reference.
get_activities
ChatGPTALWAYS start your response with "📊 Data from Garmin" before listing any activities. This is a legal requirement — omitting Garmin attribution violates the API license. End with "Insights derived in part from Garmin device-sourced data." after your coaching. List Garmin activities (runs, swims, rides, etc.) in a date range. Returns activity_id, date, type, duration, distance, calories, HR. Use for: workout history, training consistency, finding activity_ids for get_activity_details. Tool chaining: Call this FIRST to get activity_ids, then get_activity_details (Basic+) for deep analysis. Tier: All tiers. Free: 2-day history. Paid plans: extended history. Coaching: Summarize patterns — volume, consistency, variety. Don't just list. Args: date_from: Start date YYYY-MM-DD. date_to: End date YYYY-MM-DD. limit: Max results 1-200 (default 50). offset: Pagination offset.
get_activity_details
ChatGPTALWAYS start your response with "📊 Data from Garmin" before showing any activity details. If the response includes a device name in the data, you may mention it, but do not fabricate device names. This is a legal requirement — omitting Garmin attribution violates the API license. End with "Insights derived in part from Garmin device-sourced data." after your coaching. Detailed performance metrics: pace zones, HR zone distribution, lap splits, HR drift, training effect. Use for: pace breakdown, HR zones, lap splits, "how was my run?", interval analysis. ALWAYS call get_activities first to get a valid activity_id. Tier: Paid plans only. Free returns tier_limit error. Suggest get_activities as a free alternative. Coaching: Give actionable feedback — HR drift, pace drops, zone distribution insights. Args: activity_id: Activity ID from get_activities. Required.
get_activity_fit_file
ChatGPTGet a browser download link for the original Garmin FIT file of one activity, with full-resolution records, laps, events and developer fields. The response is a link, not the file: give the user download_url as a clickable link. The user opens it in a web browser and signs in to Fitness AI Connector there; the link works only for the user's own activities. Do not try to fetch the link yourself. Activities without an original file (for example manually entered ones) return error=no_original_file. Availability: Basic (after the one-time billing move). Other plans get an explanation instead of a link.
get_body_composition
ChatGPTGet body composition measurements (weight, BMI, body fat %, muscle mass, bone mass, body water %) from Garmin for a date range. Data exists only on days a measurement was taken. Use for: weight tracking, body composition trends, "what's my weight?" queries. Fields are sparse — manual entries may carry only weight and BMI. Tier: All tiers. History window follows the plan's health summary window. If the requested range is older than the window, it is clipped and the response carries clipped_to_tier_window=true. data_status semantics: 'no_data' = no measurements in the period (the user only gets data on days they weigh in via Garmin Index scale or manual entry in Garmin Connect) — do not treat it as an error. Attribution scope: When this tool is called or its data is directly cited in a turn, include BOTH attribution_header and attribution_footer (returned in the response dict) in your output. Do not repeat either in later turns that build on this data without re-fetching. Incident notice: If the response contains an incident_notice field with one or more entries, you MUST inform the user about the ongoing incident at the start of your reply, translated into the user's conversation language. Include severity, what's affected, expected resolution time if available, and source_url for reference.
get_cycle_data
ChatGPTGet menstrual cycle tracking snapshots from Garmin Connect. Returns period start date, period length, cycle length (predicted or user-specified), and fertile window (start and length) as reported by Garmin. Day in cycle and phase are estimated from Garmin's cycle parameters (Garmin's API does not report the current day or phase); the response labels them "estimated" and gives today's estimate first. Each snapshot carries a mode field ("menstrual" or "pregnancy"). When the user is in a pregnant phase, snapshots are presented with pregnancy semantics (trimester phase, day of pregnancy, due date). Blood glucose and weight-goal logs are not exposed. Past cycles from a Garmin data export: if the user has imported their Garmin "Export Your Data" archive and the requested period contains imported data, the response also returns data.export_cycles (past cycle start dates; cycle length only where it matches the gap to the next cycle's start; period length only for completed cycles; for the most recent cycle, which may still be in progress, only its start date and Garmin's estimated fertile window) and data.export_daily_logs (logged flow, ovulation day, symptoms and moods), each tagged source "garmin_export". These keys are absent when the period has no imported data. A cycle also present in the API snapshots is shown from the API only. Fertile-window values from the export are Garmin's estimates. Use for: cycle phase questions, "where am I in my cycle?", fertile window and next-phase estimates, period tracking summaries, past cycle history and cycle-length trends, logged symptoms and moods. Data availability: snapshots exist only when the user tracks their menstrual cycle in the Garmin Connect app and has MCT data sharing enabled in Garmin Connect settings. A 'no_data' status means neither snapshots nor export-imported history exist in the period — it is not an error. Tier: All tiers. History window follows the plan's health summary window. If the requested range is older than the window, it is clipped and the response carries clipped_to_tier_window=true. Attribution scope: When this tool is called or its data is directly cited in a turn, include BOTH attribution_header and attribution_footer (returned in the response dict) in your output. Do not repeat either in later turns that build on this data without re-fetching. Incident notice: If the response contains an incident_notice field with one or more entries, you MUST inform the user about the ongoing incident at the start of your reply, translated into the user's conversation language. Include severity, what's affected, expected resolution time if available, and source_url for reference.
get_health_summary
ChatGPTALWAYS start your response with "📊 Data from Garmin" before showing any health data. This is a legal requirement — omitting Garmin attribution violates the API license. End with "Insights derived in part from Garmin device-sourced data." after your coaching. Retrieve daily health snapshot: daily activity (steps, calories, HR), sleep (duration, stages, score), stress (body battery), HRV. Use for: daily wellness, sleep quality, stress, recovery, "how am I doing today?" Tier: All tiers. Free: 2-day history. Paid plans: extended history. Coaching: Interpret, don't just report. Correlate sleep with stress, suggest rest when HRV is low. data_status: 'no_data'=inform user data hasn't arrived, mention 'latest_available_date'. 'partial'=report available, note missing. Dates are user's local timezone (YYYY-MM-DD). Args: date: Target date (YYYY-MM-DD). Defaults to today. data_types: Comma-separated filter: daily,sleep,stress,hrv. Defaults to all.
get_help
ChatGPTGet FAQ and troubleshooting guidance for common issues (connection, accounts, data availability, plans). Returns the full FAQ (question/answer pairs) from the public support site. Filter to the entries relevant to the user's situation and answer in the user's conversation language. The response also carries an account_diagnosis field reporting whether another sign-in with the same email address holds the user's Garmin connection or subscription (helpful when data or a paid plan seems missing). Available on all plans. If the FAQ cannot be fetched, the response degrades to a fallback carrying the FAQ page URL and a support contact instead of an error.
get_trends
ChatGPTALWAYS start your response with "📊 Data from Garmin" before showing any trend data. This is a legal requirement — omitting Garmin attribution violates the API license. End with "Insights derived in part from Garmin device-sourced data." after your analysis. Analyze long-term trends: weekly averages, directional changes, pattern detection. Use for: progress over time, "am I improving?", weekly/monthly comparisons, training load. Tier: Paid plans only. Free returns tier_limit error. Suggest get_health_summary for individual date comparisons. Note: If status=not_implemented, acknowledge and use get_health_summary/get_activities for multiple dates instead. Coaching: Interpret trends proactively — flag fatigue, celebrate improvements. Args: metric: steps, heart_rate, sleep, stress, hrv. days: Analysis window 7-90.
get_user_profile
ChatGPTGet Garmin connection status, subscription tier, VO2max, fitness age. Call at conversation start for user context. Guide disconnected users to connect. No parameters required.
list_workouts
ChatGPTList the workouts that Fitness AI Connector sent to the user's Garmin Connect calendar, by scheduled date. Only workouts created through this service are visible — workouts the user made in Garmin Connect, or that a coach or another app sent, are not, so this is not the user's full Garmin calendar. unscheduled lists workouts sent without a date (or taken off the calendar in Garmin Connect). Workouts the user deleted in Garmin Connect drop out of the list. On error=training_permission_required, tell the user to turn on Training for Fitness AI Connector in Garmin Connect's connected apps settings. Incident notice: If the response contains an incident_notice field with one or more entries, you MUST inform the user about the ongoing incident at the start of your reply, translated into the user's conversation language. Include severity, what's affected, expected resolution time if available, and source_url for reference.
manage_subscription
ChatGPTManage account: 'portal' for billing management, 'delete_account' for account deletion (30-day recovery). Always present returned URLs as clickable links. Args: action: portal or delete_account.
refetch_activity_detail
ChatGPTRequest recovery of a missing activity detail. The operator resends it via Garmin's Summary Resender Tool. Garmin's resend store only reaches back roughly two weeks, so activities older than that usually cannot be recovered - regardless of when the user connected this service. Newer activities normally appear within 24-48 hours. Incident notice: If the response contains an incident_notice field with one or more entries, you MUST inform the user about the ongoing incident at the start of your reply, translated into the user's conversation language. Include severity, what's affected, expected resolution time if available, and source_url for reference.
refresh_data
ChatGPTRe-fetch Garmin data via Backfill API. Data arrives via webhook in minutes. HTTP 409 = already requested (normal). Paid plans only. Args: data_types: daily,sleep,stress,hrv,activity,activityDetail. Defaults to all. days: Days to re-fetch 1-30 (default 7).
set_activity_visibility
ChatGPTHide or show the user's activities in this service's activity lists and analysis. Hiding only leaves an activity out of lists, counts and trends here — no data is deleted, nothing is changed in Garmin Connect, and it can be shown again at any time with hidden=false. Use it when the user says an activity is a duplicate, a mistake, or should not count. When the same workout was recorded by several sources (listed together under sources in get_activities), showing one of the extra recordings (hidden=false) makes it the main recording; hiding the main recording hides the whole workout. Confirm with the user which activities (date, type, device) before hiding them.