Skip to main content
Glama

download_workout

Destructive

Downloads a workout in FIT format by workout ID and confirms it is available through Garmin Connect, since binary data cannot be returned directly via MCP.

Instructions

Download a workout as a FIT file

    Downloads the workout in FIT format. The binary data cannot be returned
    directly through the MCP interface, but this confirms the workout is available.

    Args:
        workout_id: ID of the workout to download
    

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": {
      "workout_id": "<workout_id>"
    },
    "name": "download_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
workout_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The description earns credit for the non-obvious disclosure that binary data cannot be returned through MCP, which is the single most important behavioral fact here. However, annotations declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, and the description explains none of that — whether a file is written to disk, where it lands, or whether repeated calls have side effects is left unaddressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The opening line and the first body sentence say the same thing twice ("Download a workout as a FIT file" / "Downloads the workout in FIT format"), and the raw Python-docstring Args block is awkward structure for a description. The middle caveat sentence is the only high-value content and it is buried.

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

Completeness3/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 should say what the caller actually receives; it gestures at this ("confirms the workout is available") but never states the response shape or whether a file path is returned. Against a non-idempotent, destructive-annotated, open-world tool, this is only minimally sufficient.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description must carry the load, and it only restates the name as "ID of the workout to download" with no format, type, or pointer to how to obtain a valid ID (e.g. via get_workout_by_id or workout listing). That adds essentially no meaning beyond the parameter name.

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?

"Download a workout as a FIT file" names a specific verb and resource, and the body clarifies the real effect: the binary never reaches the caller, only a confirmation that the workout is available. That caveat makes the stated purpose slightly at odds with what actually happens, which keeps it from a 5, but an agent can still tell what the tool targets.

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?

No when-to-use guidance at all: nothing distinguishes it from sibling download tools like download_activity_file, download_course_gpx, or set_fit_download_dir, and no prerequisites (auth, existing workout, download directory configuration) are stated. The only implicit cue is the singular workout_id argument.

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