Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

import_course_gpx

Parses a local .gpx file into a Garmin course without saving it, returning only a resampled preview track with no courseId.

Instructions

Parses a GPX file into a course WITHOUT saving it (courseId: null). Multipart POST (field file) to /course-service/course/import. Parses only, saves NOTHING: the result has courseId: null and a RESAMPLED track (13 GPX points came back as 37) with null elevations/timestamps; courseName is the GPX <name>. Only .gpx accepted (only .gpx verified); throws GarminError on an empty response.

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": {
      "filePath": "<filePath>"
    },
    "name": "import_course_gpx"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYesAbsolute path to a local .fit, .gpx or .tcx file (~ is expanded)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses the transport (multipart POST, field `file`), the endpoint, that nothing is persisted, the resampling behavior (13 GPX points return as 37) with null elevations/timestamps, and the empty-response error. One tension worth noting: readOnlyHint=false implies possible state modification while the description insists nothing is saved; the description is the more accurate account, but the mismatch is not spelled out.

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?

Front-loaded with the key fact (parse, do not save) and wastes little. It is densely packed with bold, parentheticals and a concrete numeric example (13 -> 37) that borders on over-detailed, but every sentence still carries actionable information.

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?

There is no output schema, so the description carries the return-shape burden and does so: courseId stays null, the track is resampled, elevations/timestamps are null, and courseName comes from the GPX `<name>`. Error behavior and accepted file type are also covered, so nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds a constraint the schema does not carry: only `.gpx` is accepted/verified, while the schema's own description advertises `.fit`, `.gpx` or `.tcx` for this field. That narrowing meaningfully reduces the chance of a rejected call.

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+resource (parse a GPX into a course) and immediately qualifies scope with 'WITHOUT saving it' and 'courseId: null', which separates it from the sibling create_course_from_gpx. An agent can pick between preview-parse and persist-create without opening either 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?

The 'Parses only, saves NOTHING' framing makes the use case clear (parse/preview when you do not want persistence) and the failure mode ('throws GarminError on an empty response') is stated. It never names create_course_from_gpx as the alternative when persistence is desired, so the routing guidance is implicit rather than explicit.

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