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

Icu Download Gpx File

icu_download_gpx_file
Read-onlyIdempotent

Download an Intervals.icu activity as a GPX file for GPS devices or mapping software by specifying its activity ID and optional save path.

Instructions

Download activity converted to GPX format (GPS devices, mapping software). Different from download_activity_file (original upload format) and download_fit_file (FIT 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_gpx_file"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide high behavioral context (readOnly, idempotent, etc.). The description adds valuable domain-specific context by defining the intended use case (GPS devices, mapping software) and the output format itself, enhancing the agent's understanding without duplicating structured data.

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?

The description is perfectly concise, using two sentences to deliver maximum value. The primary differentiator is stated in the first sentence, making the information highly accessible to the agent.

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?

The definition is entirely complete for its role. Given the rich annotations and schema, the description successfully provides the necessary context (format, use case, and sibling differences) required for correct invocation.

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?

With 100% schema coverage, the schema already details the parameters (`activity_id` and `output_path`). The description focuses entirely on the file format and its intended use, providing no necessary semantic information about the parameters beyond what is in the schema, thus achieving baseline adequacy.

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 clearly states the tool's function: downloading an activity converted to GPX format. It distinguishes this tool by naming its siblings and the specific format of the output, leaving no doubt about its purpose.

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

Usage Guidelines5/5

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

It provides perfect usage guidelines by explicitly contrasting the GPX format with other common formats (upload original, FIT format). This immediately tells the agent when to select this tool versus the `download_activity_file` or `download_fit_file` siblings.

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