Skip to main content
Glama

download_course_gpx

Destructive

Download a Garmin Connect course as a GPX file rebuilt from track points and waypoints, so you can save or export it for navigation or backup.

Instructions

Download a Garmin Connect course as a GPX file.

    The GPX is rebuilt from the course's track points (lat/lon/elevation)
    and course points (as waypoints); it is not the originally uploaded file.

    Args:
        course_id: ID of the course to download.
        output_path: Optional destination directory (saved as {course_id}.gpx)
            or file path ending in .gpx; any other file path is rejected.
            Defaults to the download_activity_file directory
            (GARMIN_FIT_DOWNLOAD_DIR, then set_fit_download_dir), else
            ./courses/{course_id}.gpx.
    

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": {
      "course_id": "<course_id>"
    },
    "name": "download_course_gpx"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
output_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description supplies behavior beyond them: the file is reconstructed from track points and course points, non-.gpx file paths are rejected, and the default directory resolves via GARMIN_FIT_DOWNLOAD_DIR then set_fit_download_dir then ./courses/. The one gap is that it never warns about overwriting an existing file at output_path, which is exactly what destructiveHint implies.

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?

The core behavior is front-loaded in the first two sentences, followed by parameter notes; nothing is redundant. The default-directory chain is verbose but each element changes agent behavior, so it earns its place.

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 only two parameters, no output schema, and no nested objects, the description covers purpose, file format origin, path validation, and defaults adequately. It is slightly short on the mutation side (overwrite behavior, permissions, and what exactly is returned on success).

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries full burden and does: course_id is the course to fetch, and output_path accepts either a directory (saved as {course_id}.gpx) or a .gpx file path, rejects other file paths, and has a documented default resolution chain. That is meaningfully more than the bare `string` schema.

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 ("Download a Garmin Connect course as a GPX file") and adds the important qualifier that the GPX is rebuilt from track points and course points rather than being the original upload. It does not explicitly contrast with siblings like download_activity_file or download_workout, but the course scope is unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to choose this tool over download_activity_file, get_course_details, or upload_course, nor any prerequisites (auth, course ownership). Using the download_activity_file default directory as the fallback hints at a relationship but does not tell the agent when to prefer one tool.

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