ownmetrics-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_daily_overviewA | T1. One day's overview: steps, distance, floors, resting/min/max heart rate, stress, Body Battery, calories, intensity minutes, sleep hours and sleep score. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero. |
| get_sleepA | T2. Sleep per night over a date range: hours, deep/light/REM/awake minutes, sleep score, Garmin's feedback, average heart rate, respiration and sleep stress. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero. |
| get_hrvA | T3. Heart rate variability (HRV) per night over a date range: last-night average, weekly average, 5-minute high, status and personal baseline, in milliseconds. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero. |
| get_stress_and_body_batteryA | T4. Per day over a date range: average stress (0-100), minutes in each stress band, and Body Battery high, low, charged and drained. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero. |
| get_heart_rateA | T5. One day's heart rate (resting, min, max, 7-day resting average) and the user's heart rate zones. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero. |
| list_activitiesA | T6. List activities in a date range, newest first, optionally filtered by Garmin activity type key (e.g. running, cycling, indoor_cycling, lap_swimming, strength_training). Returns ids for get_activity. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero. |
| get_activityA | T7. Details of one activity by id: duration, distance, pace, speed, heart rate, power, cadence, training effect and load, splits and structured workout steps. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero. |
| get_body_metricsA | T8. Body metrics over a date range: weigh-ins (kg), BMI, body fat, hydration; plus Pulse Ox (SpO2) and fitness age as of the end date. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero. |
| get_account_statusA | T9. Check the Garmin connection: whether the key works, granted scopes, a warning if the key expires within a day, which data areas respond, and what Garmin does not provide. Use this first when something fails. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target clearly distinct data areas: stress/body battery, heart rate, sleep, HRV, activities, body metrics, and account status. The main overlap is that get_daily_overview aggregates heart rate, stress, Body Battery, and sleep, which can be confused with the dedicated metric tools, though the descriptions distinguish one-day summary from range-specific detail.
All tool names follow a consistent snake_case verb_noun pattern, using get_* for metric retrieval and list_* for collections. There are no mixed conventions or vague verbs.
Nine tools is well-scoped for a read-only Garmin health and fitness data server. Each tool covers a distinct data area or essential diagnostic function, and none appear redundant.
The surface covers core health metrics (sleep, HRV, heart rate, stress, Body Battery, body metrics), activity listing and detail retrieval, and account diagnostics. Minor gaps exist for specialized Garmin metrics like training readiness, VO2 max, or planned workouts, but core workflows are covered.