Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_activity_splits

Read-only

Retrieve even-distance splits for a Garmin activity with time, pace, heart rate, cadence, power, and elevation per split; excludes paused time and supports custom split length in meters.

Instructions

Even distance splits of one activity (per km by default), computed from the recorded data: time, pace, average/max heart rate, cadence, power and elevation gain/loss per split. Paused time is excluded. The last split is usually shorter. Needs distance data.

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

Input Schema

NameRequiredDescriptionDefault
activity_idYesActivity ID from search_activities (a positive integer).
split_metersNoSplit length in meters, e.g. 1000 or 1609.34.

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 and openWorldHint, so the bar is lower, yet the description still adds meaningful behavior: paused time is excluded, the final split is usually shorter, and the tool requires distance data to work. It does not discuss error behavior when distance data is absent, which keeps it from a 5.

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?

Three short sentences, front-loaded with what the tool returns, followed by the two behavioral caveats. No filler, though the metric list is somewhat dense and could be trimmed given the output schema exists.

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 two-parameter read-only tool with a full output schema, the description covers purpose, computation basis, and the key caveats. The only gap is the absence of routing guidance relative to lap- or summary-level siblings.

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 coverage is 100%, so both parameters are already documented, including the 1000m default and the 1609.34 example. The description's 'per km by default' merely restates the schema default rather than adding new meaning, 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?

States a specific verb and resource: even distance splits of one activity, with the default split length and the metrics computed per split. It is clearly distinguishable from a whole-activity or lap-level tool, though it never names a sibling to contrast with.

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?

Provides one real prerequisite ('Needs distance data') and implies usage via 'computed from the recorded data', but gives no explicit when-to-use versus when-not guidance, e.g. splits versus laps or versus summary stats.

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