Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

download_activity

Idempotent

Saves a Garmin activity's raw GPS and sensor file to your local download directory and returns its path for analysis or backup.

Instructions

Download an activity's raw file (GPS track, sensor data) to the local download directory and return its path. Reads from Garmin; only writes a local file.

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": "download_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOne of: ORIGINAL (zip with the FIT file), TCX, GPX, KML, CSVTCX
activity_idYesGarmin activity ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds important context beyond those flags: the operation reads from Garmin but only writes a local file, which reassures the agent that remote data is not mutated. It does not cover overwrite behavior or the exact local directory, but it adds meaningful behavioral clarity.

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?

Two tightly written sentences with no wasted text. The core action and scope are front-loaded, followed by the key read-versus-write clarification.

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?

With an output schema, full parameter coverage, and annotations, the definition supplies enough context to call the tool correctly. Minor gaps remain around overwrite behavior and the exact local download directory, but nothing critical is missing.

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%, so the schema already documents activity_id and the format options (ORIGINAL, TCX, GPX, KML, CSV). The description adds no parameter-level detail beyond the schema, so the baseline of 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?

The description states a specific verb and resource: 'Download an activity's raw file (GPS track, sensor data)' and clarifies it writes to the local download directory and returns the path. This clearly distinguishes it from the many get_* siblings that return parsed Garmin data rather than raw files.

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 gives clear usage context: raw file download, reads from Garmin, local-only write. It does not explicitly name alternatives such as get_activity_details for parsed data or state when not to use this tool, so it falls short of full when/when-not guidance.

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

Deploy Server

Other Tools