MCP tools & capabilities

List the user's Garmin activities, most recent first. Optionally filter by activity type and date range. Returns compact rows (id, type, name, start_time, duration_s, distance_m, calories, avg_hr) plus the total count for pagination.

Full detail for a single activity by its garmin_activity_id: the complete summary plus splits, typed splits, HR zones and weather. Use garmlink_activity_timeseries for the sample-by-sample data.

Downsampled sample-by-sample series for an activity (heart_rate, pace/speed, altitude, power, cadence, temperature, GPS…). Buckets to <= `points` samples with per-bucket averages, and always reports the true global min/max/avg per field. Full 1 Hz data lives in the raw FIT; this is LLM-sized.

Aggregated training volume over a date range, grouped by sport, month or ISO week: activity count, total distance (km), duration (h), calories and average HR per bucket.

Daily sleep summaries, newest first — one compact object per night: total_min and per-stage minutes (deep_min/light_min/rem_min/awake_min), sleep score, plus overnight avg_spo2, avg_respiration, resting_hr and overnight_hrv when measured. THE tool for sleep quality, duration and recovery-trend questions. Hollow (unmeasured) nights are omitted.

Daily heart-rate-variability summaries, newest first: last_night_avg (overnight rMSSD, ms), weekly_avg and HRV status (BALANCED/UNBALANCED/LOW/…). THE tool for autonomic recovery / readiness trends. For the raw per-reading series use garmlink_daily_metric_get(family:'hrv', full:true).

Daily all-day stress summaries, newest first: avg and max stress level (0-100). Use to see how stress load evolves across days. For time-in-zone (rest/low/medium/high) durations or the per-minute series use garmlink_daily_metric_get(family:'stress', full:true).

Daily Body Battery summaries, newest first: charged and drained totals (energy points gained resting/sleeping vs spent) for the day. Use to relate energy reserves to sleep, stress and activity. For the day's high/low Body Battery levels or the intraday series use garmlink_daily_metric_get(family:'body_battery', full:true).

Daily step totals, newest first: total steps walked that day. Use to track daily movement. Distance and floors for the day are on garmlink_daily_summary_get; for the step goal or intraday buckets use garmlink_daily_metric_get(family:'steps', full:true).

Daily heart-rate summaries, newest first: resting, min and max HR (bpm) for the day. Use to track resting-HR trends and daily cardiac load. For the intraday HR series use garmlink_daily_metric_get(family:'heart_rate', full:true).

Daily respiration summaries, newest first: avg (waking) plus min and max breaths per minute. Use to monitor breathing-rate trends and recovery.

Daily pulse-ox (SpO2) summaries, newest first: avg and low blood-oxygen saturation (%). Use for altitude acclimation and overnight oxygen trends.

Daily floors summaries, newest first: floors ascended and descended that day. Use to track vertical movement.

Daily intensity-minutes summaries, newest first: the day's moderate_min and vigorous_min plus the running weekly_total against the week_goal. Use to check adherence to activity-intensity guidelines.

Daily hydration records, newest first: fluid intake versus goal and sweat-loss estimates (ml). Use to track hydration habits.

Daily blood-pressure records, newest first: systolic/diastolic readings and pulse from Garmin Index BPM or manual entries. Use to track blood-pressure trends.

The single-glance all-day rollup, newest first — one compact object per day combining steps, calories, distance_m, active_min and floors. Use this FIRST for a day-level overview or multi-metric daily trend, then drill into a specific family (garmlink_sleep_get, garmlink_stress_get, …) for its detail.

Generic escape hatch: fetch any Garmin daily family by name over a date window, newest first. Returns the same COMPACT per-day summary as the dedicated getters by default; pass full:true to get the RAW record (all intraday arrays) — only for a single family over a NARROW window, as raw payloads are large. Prefer the specific getter (garmlink_sleep_get, garmlink_stress_get, …) when one exists; use this for families without a dedicated tool such as training_readiness, all_day_events, nutrition or menstrual. Returns an error object listing valid families if the name is unknown.

Garmin Training Status snapshots over time (productive, maintaining, peaking, overreaching, detraining, recovery, unproductive…), with acute/chronic load balance and load focus. Use to judge whether the user is training productively or needs recovery.

History of Garmin max-metrics snapshots — chiefly VO2max (running and cycling) and related fitness estimates. Use to track cardiovascular fitness trends over weeks and months.

Garmin Fitness Age snapshots and the contributing factors Garmin exposes (VO2max, resting HR, activity intensity, body composition where available). Use to show how the user's estimated fitness age is trending.

Garmin's predicted race finish times (5K, 10K, half-marathon, marathon) captured over time. Use to gauge current running performance potential and its trajectory.

Garmin Endurance Score snapshots — the composite measure of the user's ability to sustain effort over long durations, with its level/category. Use to track endurance development over time.

Garmin Hill Score snapshots — the measure of climbing strength and endurance on uphill efforts, with its category. Use to track how the user's hill/climbing ability is progressing.

Garmin personal records snapshots (fastest 1K/5K/10K, longest run/ride, most ascent, best power, etc.). Use to report the user's all-time bests and when they were set.

Garmin body-composition snapshots (weight, BMI, body fat %, muscle mass, bone mass, body water, etc.), typically from a connected smart scale. Use to track weight and composition trends over time.

The user's currently configured training zones: heart-rate zones, power zones and cycling FTP (each the latest snapshot). Use to interpret zone-based effort in activities or to prescribe target zones.

No arguments.

Daily Garmin Training Readiness, newest first — one compact object per day: score (0–100), level (LOW/MODERATE/HIGH/…), the underlying sleep_score and recovery_min (recovery time). Use to advise whether today is a good day for a hard session or for recovery.

List the user's Garmin gear snapshots (shoes, bikes and other tracked equipment) with accumulated mileage/usage. Most recent snapshot first. Use to answer questions about how far a pair of shoes or a bike has been ridden/run, or when gear was retired.

List the user's registered Garmin devices (e.g. Fenix 8, HRM straps, bike computers) as captured snapshots, most recent first. Use to know which watch/sensors are paired, firmware/model details, and which device recorded the data.

The user's latest Garmin profile snapshot: display name, personal details, physiological settings and preferences. Returns the single most recent snapshot.

No arguments.

Garmin connection state plus last successful sync time and the most recent sync runs (status, scope, timing, counts). Call this FIRST whenever data seems missing, empty or stale — it tells you whether the account is connected, when it last synced, and whether a sync is currently running or recently failed.

No arguments.

Triggers an on-demand Garmin sync to pull the freshest watch data. Rate-limited to at most once per 15 minutes; if a sync ran recently it returns status:rate_limited with retry_after_s. Non-destructive — it only fetches and appends new data, never deletes anything. Returns {status:'started', sync_run_id} on success. Requires a connected account; returns {error:'not_connected'} otherwise.

No arguments.

List the user's stored golf-round summaries (scores, handicap, course stats), most recent first. Use when the user asks about their golf performance or rounds played.

List the Garmin badges the user has earned (challenges, milestones, streaks), most recent first. Use when the user asks about achievements, badges or Garmin challenges.

List the user's Garmin goals (step targets, distance/activity goals and their progress), most recent first. Use when the user asks about the goals they set or how close they are to hitting them.

Daily nutrition logs (calories in, macros, water/food entries) per day, newest first, optionally bounded by a date range. Use when the user asks about their food intake, calories consumed or macros over time.

Daily menstrual-cycle tracking (cycle phase, day, logged symptoms) per day, newest first, optionally bounded by a date range. Use when the user asks about their cycle tracking.

Fetch ANY stored snapshot by its kind so every synced snapshot type is reachable, even those without a dedicated tool. Returns the most recent snapshots for that kind first. Use this as the catch-all when a more specific tool doesn't exist.