Skip to main content
Glama
Sign In
Garmin Connect MCP Server

Garmin Connect MCP Server

by sedoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Upload Activity

upload_activity
Destructive

Upload a FIT, GPX, or TCX activity file directly to Garmin Connect. Sync your recorded workouts for analysis and tracking.

Instructions

Upload an activity file (FIT, GPX, TCX format) to Garmin Connect.

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

Input Schema

NameRequiredDescriptionDefault
filePathYesFull path to the activity file (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.3.0

TDQS

A3.6/5.0
Behavior2/5

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

While annotations indicate 'openWorldHint' and 'destructiveHint', the description itself does not disclose side effects, potential impact on existing data, or any required context. It only states the action without discussing consequences or limitations.

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 a single, concise sentence with no redundancy or irrelevant details. It conveys the essential information efficiently.

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?

The description is adequate for a simple upload action, but it does not mention output, error handling, or any follow-up steps. Given there is no output schema, a bit more context on expected results would improve completeness.

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?

The single parameter 'filePath' is fully described in the schema with 'Full path to the activity file', and the description reinforces the file format expectation. Parameter coverage is 100% and meaning is unambiguous.

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 action (upload), the resource (activity file), and the accepted formats (FIT, GPX, TCX). It is distinct from sibling tools, which are mostly retrieval or mutation operations on existing data.

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?

The description does not specify when to use this tool versus alternatives, nor does it mention any preconditions or scenarios where it should or should not be used. No explicit guidance on when to choose this over other tools.

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