Skip to main content
Glama

upload_course

Upload a GPX file as a Garmin Connect Course so you can load it on your watch for navigation or build a PacePro strategy.

Instructions

Upload a GPX file as a Garmin Connect Course.

    The course can then be loaded onto the watch (sync or "Send to Device")
    and used as a navigation course or to build a PacePro strategy.

    Args:
        gpx_path: Absolute path to the .gpx file on disk.
        course_name: Override the course name. Defaults to the name parsed
            from the GPX file. Max 128 characters; Garmin rejects longer.
        activity_type: One of running, cycling, hiking, walking, trail_running,
            mountain_biking, road_biking, gravel_cycling. Defaults to running.
        description: Optional description shown on the course detail page.
            Max 512 characters; Garmin rejects longer.
    

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": {
      "gpx_path": "<gpx_path>"
    },
    "name": "upload_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpx_pathYes
course_nameNo
descriptionNo
activity_typeNorunning

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the write, non-idempotent, open-world profile, so the description usefully adds validation constraints the agent would otherwise hit blind: 128-char course name limit and 512-char description limit, both enforced with rejection by Garmin. It does not say what happens on re-upload of the same file or on a missing/invalid GPX, which is the remaining gap.

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 purpose is front-loaded and the Args block is scannable with no filler. The nesting of per-parameter rationale under each arg is efficient, though the docstring-style formatting is slightly verbose.

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?

Input side is thorough, but with no output schema and no statement of return values, an agent does not know whether it gets a course ID or an upload status back, and there is no mention of error behavior for invalid or oversized input. For an upload tool with an open-world, non-idempotent profile, that leaves the agent under-informed about the result.

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 the full burden and does it well: it defines gpx_path as an absolute on-disk path, explains course_name as an override with its 128-char cap, lists the accepted activity_type values (absent from the schema as an enum) plus the 'running' default, and documents the 512-char description cap.

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 first sentence states a specific verb and resource: 'Upload a GPX file as a Garmin Connect Course.' It also explains the resulting object's purpose (navigation course or PacePro strategy), making it clearly distinct from upload_workout and download_course_gpx.

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

Usage Guidelines3/5

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

It explains what the uploaded course is for (sync to watch, navigation, PacePro), which implies when to use it, but never states when to prefer this over siblings like upload_workout or how it relates to download_course_gpx. No prerequisites or exclusions are given.

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