Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_activity_laps

Read-only

Retrieve lap-by-lap details from a Garmin activity’s FIT file, including distance, pace, heart rate, cadence, power, and intensity, to analyze intervals and structured workout reps.

Instructions

Laps of one activity from its FIT file: distance, timer time, pace (or speed), grade- adjusted pace, average/max heart rate, cadence, power, ascent/descent, intensity (active, rest, warmup, cooldown) and what ended the lap (manual, distance, time). For structured workouts and intervals, laps are the reps.

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_laps"
  }
}

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine context beyond that: data provenance (parsed from the FIT file), the intensity taxonomy (active, rest, warmup, cooldown), and the lap-trigger vocabulary (manual, distance, time), which tells the agent what 'lap' actually means in this data. It stops short of noting behavior for activities lacking FIT/lap data, which is the main residual gap.

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?

Two sentences, front-loaded with the core statement of what is returned, followed by a short interpretive note about intervals. The long field enumeration is dense but each item earns its place as a return-content specification; nothing is padding.

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?

An output schema exists, so the description needn't restate return structure, and it still covers semantics (what a lap is, how laps relate to reps) that the schema would not convey. For a single-parameter read tool with full schema coverage, this is nearly complete; only edge behavior (activities without laps) is unaddressed.

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 parameter activity_id is fully documented in the schema ('Activity ID from search_activities (a positive integer)'). The description adds no additional meaning about that parameter, so the baseline of 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?

States a specific verb+resource: 'Laps of one activity from its FIT file', then enumerates exactly what each lap contains (distance, timer time, pace, GAP, HR, cadence, power, ascent/descent, intensity, lap trigger). An agent can tell this is the per-lap breakdown tool. It does not explicitly differentiate itself from the close sibling get_activity_splits, which keeps it at 4 rather than 5.

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 implied rather than stated: 'For structured workouts and intervals, laps are the reps' signals when lap granularity is the right choice. There is no explicit when-not guidance and no named alternative such as get_activity_splits or get_activity_summary_stats for aggregate views, so the agent must infer routing.

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