Skip to main content
Glama

downloadActivityFit

Downloads the original .FIT file for a Garmin activity, saving it to your computer and returning the absolute path with second-by-second HR, cadence, speed, and laps. Later calls reuse the file.

Instructions

Download the ORIGINAL .FIT file of an activity and save it on the user's computer. Returns the absolute path of the saved .fit file (second-by-second HR, cadence, speed, laps). The file is saved once in the fit folder of the data dir; a later call does not download it again. Use it only when the user wants the file itself: getActivityLaps and getActivitySets already read it.

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": {
      "activityId": "<activityId>"
    },
    "name": "downloadActivityFit"
  }
}

Input Schema

NameRequiredDescriptionDefault
activityIdYesGarmin activity id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses that a file is written to disk, where it lands ('fit folder of the data dir'), that the return value is the absolute path, and that repeat calls reuse the cached file rather than re-downloading. It omits failure behavior when the activity id is invalid or the download fails, and any size or auth caveats, which keeps it short of 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.

Conciseness5/5

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

Four short sentences, front-loaded with the action and return value, then caching behavior, then the sibling routing note. The parenthetical about second-by-second HR, cadence, speed and laps is the only optional content and it usefully characterizes the payload.

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

Completeness5/5

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

A one-parameter tool with full schema coverage, no output schema, and no annotations. The description nevertheless covers the return value (absolute path), file location, idempotent caching, and when to prefer siblings, leaving nothing an agent needs to call it correctly.

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 activityId is already documented as the 'Garmin activity id' in the schema. The description adds no further constraints or format guidance for that parameter, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource: 'Download the ORIGINAL .FIT file of an activity and save it on the user's computer.' It also distinguishes itself from siblings by noting that getActivityLaps and getActivitySets already read the file, so an agent can tell this is the raw-file tool rather than a data-access tool.

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

Usage Guidelines5/5

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

Gives an explicit gate: 'Use it only when the user wants the file itself,' and names the alternatives (getActivityLaps, getActivitySets) that already cover the read case. Both the when-to-use and when-not-to-use conditions are present, so no inference is required.

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