Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GARMIN_API_KEYYesYour Garmin Personal API key (starts with GCDC_). Can also be provided via the OS keychain or the file ~/.config/garmin/connect-personal-api-key.
GARMIN_HEALTH_DATA_DIRNoOverride the directory where the short-lived access token and history database are stored (defaults to ~/.garmin-health-mcp/).

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
morning_checkA

Recovery snapshot: last night's sleep, HRV vs baseline, resting HR vs its 7-day mean, Body Battery at wake, modelled recovery hours left, training load (acute/chronic ratio, fitness/fatigue/form), yesterday's calories and stress, and a readiness estimate shaped like Garmin's Training Readiness (sleep, recent sleep, HRV status, recovery time, acute load, recent stress). For today it is evaluated now, so it counts this morning's workouts. Garmin's real Training Readiness is not in the API: when the user mentions their Garmin readiness score, call log_garmin_readiness so the estimate calibrates to it.

log_garmin_readinessA

Record the Training Readiness score Garmin shows (0-100), stored locally, so the estimate calibrates to it (an offset at first, a fitted slope from 4 scores). Log it whenever the user mentions their Garmin readiness. Readiness drops after workouts, so log it close to when it was read.

readiness_historyB

Per-morning readiness estimate (at wake) next to its main inputs and any Garmin readiness scores logged, to judge how well the model tracks Garmin.

training_loadC

Training load: daily load, Garmin-style acute load and acute:chronic ratio (Garmin's optimal band is 0.8-1.5), fitness/fatigue/form (CTL/ATL/TSB), a status label, weekly totals (sessions, hours, distance, load, active kcal, minutes per HR zone and power zone), and load by sport.

load_focusB

Approximate Garmin Load Focus: training load split into low aerobic, high aerobic and anaerobic over the last days days.

activitiesB

Activities, newest first: type, duration, distance, Garmin training load, aerobic/anaerobic Training Effect and label, active kcal, HR, power (avg / normalised / best 20 min), elevation, minutes in HR zones 1-5 and power zones 1-7, and modelled recovery hours. activity_type filters by Garmin type key, e.g. running, cycling, virtual_ride.

activityB

Full Garmin detail for one activity (Garmin's summary DTO).

power_profileB

Cycling power: FTP (set with set_athlete, otherwise estimated as 95% of best 20-min power), best powers 5 s-60 min over days and the last 28 days, W/kg if weight is set, Coggan power zones in watts, and 5-min / 60-min to FTP ratios.

set_athleteB

Store FTP and body weight locally (used for power zones and W/kg).

dailyC

Everything known per day: sleep, HRV, resting HR, Body Battery, stress, calories, steps, training load, form, recovery and readiness estimate.

caloriesC

Daily calories burned: active, resting, total, and from recorded activities, with averages.

weekly_reportB

Week-by-week (Monday start): averages of sleep score and hours, HRV, resting HR, stress, Body Battery at wake, active kcal and steps; totals of training hours and load; end-of-week fitness and form.

list_metricsA

Daily metrics available to timeseries, chart and dashboard_data.

timeseriesB

Aligned daily series for chosen metrics (see list_metrics) with an optional rolling mean of smooth days, plus per-metric last/mean/min/max and linear trend per week. Examples: hrv, rhr, sleep_score, bb_wake, stress, active_kcal, load, acwr, ctl, tsb, readiness_est.

chartB

PNG chart of up to 6 daily metrics as stacked panels on a shared date axis: points or bars for raw values, a line for the rolling mean. HRV gets its balanced band shaded; readiness_est shows logged Garmin scores. Good sets: ["hrv","rhr","sleep_score","readiness_est"], ["load","acute_load","ctl","tsb"], ["active_kcal","steps","stress"].

dashboard_dataB

Compact JSON bundle for building a dashboard (e.g. an HTML artifact with charts): today's snapshot, aligned daily series for the key metrics, weekly rollups, load focus, the last 30 days of activities and the power profile. Embed it as data in the page rather than re-deriving numbers. Series values are null where Garmin has no data.

hrv_nightB

One night's HRV in detail, including the 5-minute readings.

intradayA

Intraday curve for one day. what: "heart_rate" (resting/min/max plus HR about every 12 minutes) or "body_battery" (level through the day plus Garmin's charge/drain events).

fitness_profileB

Garmin fitness age (with the changes that would lower it) and heart-rate zones.

syncA

Refresh the local history for the last days days. Other tools sync on their own; use this for a first long backfill (e.g. 365 days) or after the watch syncs.

api_getA

Raw GET against the Personal API for data without a tool, e.g. /weight-service/weight/range/{start}/{end}, /usersummary-service/stats/hydration/daily/{start}/{end}, /wellness-service/wellness/daily/spo2acclimation/{date}, /userprofile-service/userprofile/settings. Paths outside Garmin's allowlist return 404 (Training Readiness/Status, PRs, workouts, badges).

Prompts

Interactive templates invoked by user choice

NameDescription
morning_briefingHow recovered am I and what should today's training look like?
weekly_reviewReview the last few weeks of recovery and training.
build_dashboardMake an interactive health and training dashboard from my Garmin data.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 21 tools

Disambiguation4/5

Most tools target clearly distinct slices of data (per-activity detail vs activities list, power vs load, readiness logging vs readiness history). Some overlap exists among the aggregate/view tools (daily, weekly_report, timeseries, dashboard_data, chart) and between morning_check and daily, but the descriptions do a good job of separating their intended uses.

Naming Consistency4/5

All names are consistently snake_case and readable. The only deviation is a mix of noun-only names (activities, daily, calories, intraday, sync) and verb-led names (log_garmin_readiness, set_athlete, list_metrics, load_focus), which is minor and does not impede understanding.

Tool Count4/5

21 tools is on the high side, but each maps to a distinct Garmin data domain (sleep/HRV, load, activities, power, readiness, charts, sync). There is mild redundancy among the aggregation/view tools (chart, dashboard_data, timeseries, weekly_report), but the surface is not bloated arbitrarily.

Completeness4/5

Coverage is broad: recovery, sleep, HRV, load, activities, power, readiness estimation/calibration, plus a raw api_get escape hatch for gaps like weight/hydration/SpO2. The main gaps are native Garmin Training Readiness/Status (explicitly unavailable) and write/fitness-management operations, but core read workflows are covered.

Maintenance

ActivityMaintained
ResponsivenessOutdated data