garmin-mcp

Overview Schema Source Related Servers Discussions Admin

garmin_create_activity

Log an activity your Garmin watch didn't record by adding its type, date, start time, duration, distance, and name to Garmin Connect in your account's time zone.

Instructions

Add a manual activity (one the watch didn't record), in the account's time zone.

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": {
      "type_key": "<type_key>",
      "duration_minutes": "<duration_minutes>"
    },
    "name": "garmin_create_activity"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No	YYYY-MM-DD, 'today' or 'yesterday'	today
`name`	No
`type_key`	Yes	e.g. running, walking, strength_training, yoga
`start_time`	No	HH:MM local	09:00
`distance_km`	No
`duration_minutes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write-but-not-destructive profile is known. The description adds that the activity is stamped in the account's time zone, which is genuinely useful context, but says nothing about validation failures, duplicate handling, or what is returned after creation.

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?

A single compact sentence that leads with the action and immediately qualifies it. Nothing is redundant, though the time-zone detail could be tighter or paired with equally useful behavior notes.

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?

For a creation tool with six parameters, two required, no output schema, and only half the schema documented, the description is barely sufficient. It covers the intent and time-zone semantics but leaves return behavior and half the parameters unexplained.

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

Parameters2/5

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

Schema description coverage is only 50%, and the description supplies no parameter meaning at all. The undocumented parameters (name, distance_km) and the required duration_minutes get no clarification on units, expectations, or how type_key values are resolved beyond the schema's example list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Add a manual activity') and qualifies it as one the watch didn't record, which separates it from reading existing recorded activities. It stops short of differentiating it from siblings like garmin_create_workout or garmin_update_activity.

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?

The parenthetical '(one the watch didn't record)' implies the use case: backfilling activities that were not auto-recorded. There is no explicit guidance on when to prefer this over garmin_create_workout or garmin_update_activity, and no prerequisites or exclusions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.