Skip to main content
Glama
garmin-connect-mcp

garmin-connect-mcp

by Samiu1

Download Activity File

garmin_download_activity_file
Idempotent

Download a Garmin Connect activity's original ZIP file to a local path using its activity ID, with optional overwrite. Use it to archive or process FIT/GPX/TCX data offline.

Instructions

Download an activity's original file from Garmin as a ZIP and save it to disk.

Garmin serves these as a ZIP archive containing the FIT file (and sometimes GPX/TCX). The ZIP is written to output_path and the tool reports the path and size; the file contents are not returned to the model.

Use garmin_search_activities to find activity IDs.

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>",
      "output_path": "<output_path>"
    },
    "name": "garmin_download_activity_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
overwriteNoReplace output_path if a file is already there
activity_idYesGarmin activity ID, e.g. 123456789
output_pathYesAbsolute path to write the ZIP to, e.g. '/Users/me/Downloads/run.zip'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, it discloses where the bytes land, that the ZIP contents are not returned to the model, and what the archive typically contains (FIT, sometimes GPX/TCX). That is valuable context for a write-to-disk operation, though it does not discuss failure modes (missing activity, existing file when overwrite is false) beyond what the schema implies.

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 destination, then the archive detail, then the ID-discovery pointer. No filler or repetition of the schema.

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?

With no output schema, the description compensates by stating what is reported back (path and size) and that file contents are not returned. Combined with the annotations and fully documented schema, an agent has everything needed to invoke this correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds meaning by explaining that output_path receives the ZIP and that the tool reports the path and size, clarifying what the parameter produces. The overwrite flag is left to the schema, which documents it adequately.

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?

Specific verb and resource ('Download an activity's original file from Garmin'), plus the concrete form (ZIP saved to disk) and the destination (output_path). It clearly distinguishes itself from metadata-oriented siblings like garmin_get_activity.

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

Usage Guidelines4/5

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

It explicitly routes the agent to garmin_search_activities to obtain activity IDs, which is the key prerequisite. It does not state when to prefer this over garmin_get_activity (file vs. activity data), so the guidance is clear but not exhaustive.

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