Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by wiande00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

garmin_training

Read-only

Fetch daily Garmin training readiness, recovery time, load balance, VO2max, race predictions, and threshold/FTP data to guide workout planning.

Instructions

Training state on a day (default today). readiness: every training-readiness reading that day, with its factors; morning_readiness: the one after waking. recovery_time: hours still needed. status: training status, weekly load, acute/chronic load, ACWR, form, VO2max. load_balance: four-week aerobic low/high and anaerobic load against targets. Also fitness_age, vo2max, acclimation (heat/altitude), running_tolerance, race_predictions (5k to marathon), lactate_threshold, cycling_ftp.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "metric": "<metric>"
    },
    "name": "garmin_training"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, 'today' or 'yesterday'today
detailNofull = Garmin's raw payloadsummary
metricYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that 'readiness' returns every reading that day with factors and that 'recovery_time' is hours still needed, which is genuine return-content context, but it says nothing about missing data, historical date limits, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the scope in the first line, then a compact metric glossary with no filler. The semicolon-fragment style is dense and occasionally terse ('Also fitness_age...'), but every line carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, single-metric fetch with no output schema, the description supplies enough to select a metric and understand the gist of what comes back. Gaps are minor: no behavior for dates with no data, no note on whether metrics like race_predictions are day-scoped or rolling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

This is the description's core contribution: it defines what all twelve enum values actually mean (weekly load, ACWR, form, four-week aerobic low/high and anaerobic load vs targets), which the schema lists only as bare names. The 'date' default and format are covered by the schema, but the metric semantics are entirely description-dependent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line names the resource and scope ('Training state on a day (default today)'), and the metric list makes clear this is a single-day, metric-selectable fetcher. It never names the sibling it is not (garmin_status, garmin_trend, garmin_activity_analysis), so an agent must infer the boundary from the metric names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the default 'today' and the per-metric glosses hint at when each metric is appropriate, but there is no explicit when-to-use or when-not-to-use guidance. With siblings like garmin_status, garmin_trend and garmin_wellness likely overlapping, the description gives no rule for choosing between them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools