Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_activity_summary_stats

Read-only

Retrieve session summary stats from a Garmin activity's FIT file, including distance, pace, heart rate, cadence, power, training effect, running dynamics, and respiration.

Instructions

Session summary from the activity's FIT file: distance, timer and elapsed time, pace and best pace (or speed), grade-adjusted pace, heart rate, cadence, power (avg, max, normalized), ascent/descent, calories, aerobic and anaerobic training effect, training load, running dynamics (ground contact time and balance, vertical oscillation and ratio, step length), respiration rate, perceived effort and feel, and which data the file contains.

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": {
      "activity_id": "<activity_id>"
    },
    "name": "get_activity_summary_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYesActivity ID from search_activities (a positive integer).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the description only needs to add context. It does add two useful facts: the data source is the activity's FIT file, and the response also reports "which data the file contains," warning the agent that fields may be absent. It does not say what happens when the FIT file is missing or when a metric was not recorded.

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?

One front-loaded sentence opens with the source and scope, then lists metrics compactly. The metric enumeration is long but each item is a genuine discovery aid (e.g. running dynamics, training effect) rather than filler.

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

Completeness3/5

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

An output schema exists, so the description's value should come from scope and usage, yet most of its length restates return contents that the output schema already covers. It is adequate for a single-parameter read tool, but it leaves the agent without guidance on how this summary differs from the other activity endpoints.

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

Parameters3/5

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

Schema description coverage is 100% and the single activity_id parameter is fully documented in the schema, including its positive-integer constraint and provenance. The description adds nothing about the parameter, so baseline 3 applies.

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?

"Session summary from the activity's FIT file" names the verb-equivalent action (retrieve session summary) and the resource (an activity's FIT file), then enumerates the concrete metrics covered. It is clear what the tool returns, though it never names a sibling such as get_activity or get_activity_laps to disambiguate where the summary stops and per-lap data begins.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternatives, even though the sibling list contains obvious overlap candidates (get_activity, get_activity_laps, get_activity_splits). The only routing hint (activity_id comes from search_activities) lives in the schema, not the description.

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