Skip to main content
Glama
intervals-icu-mcp
by hhopke

Icu Download Fit File

icu_download_fit_file
Read-onlyIdempotent

Download a specific activity as a FIT file for Garmin and most training platforms, optionally saving it to a chosen path.

Instructions

Download activity converted to FIT format (Garmin / most training platforms). Different from download_activity_file (original upload format) and download_gpx_file (GPX format).

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

Input Schema

NameRequiredDescriptionDefault
activity_idYesActivity ID to download
output_pathNoPath to save the FIT file (optional)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds that the output is a converted FIT representation rather than the original upload, which is useful context, but says nothing about writing to output_path, overwriting an existing file, or failure modes. With annotations carrying the main burden, a 3 is appropriate.

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 compact sentences with zero filler; the purpose comes first and the sibling differentiation follows immediately. Every clause 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 an output schema present, return-value explanation is not required, and the description covers purpose and sibling selection adequately for a simple two-parameter download tool. It is slightly incomplete in not mentioning that the file can be saved to disk via output_path, which is the only remaining ambiguity.

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 coverage is 100%, so activity_id and output_path are fully documented in the schema including the optional/null default. The description adds no syntax, format, or path-behavior detail for either 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 (download/convert) and resource (activity) plus the output format (FIT), and explicitly names the two sibling tools it differs from with their formats. An agent can pick this over icu_download_activity_file and icu_download_gpx_file without opening any schema.

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 selection context by contrasting the three download variants and noting FIT targets Garmin/most training platforms, which implicitly tells the agent when to pick this one. No explicit 'when not to use' or prerequisite (e.g. activity must exist) is stated, so it falls short of a 5.

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