Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by marcelfortmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_activity

Retrieve a single Garmin Connect activity by ID and choose which data to include, such as summary, splits, weather, GPS/HR/power streams, heart-rate zones, or exercise sets.

Instructions

Data for a single activity by activityId. Pick via include: summary, splits, weather, details (GPS/HR/power streams), hr_zones, exercise_sets.

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": {
      "activityId": "<activityId>"
    },
    "name": "get_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoWhich parts to return. Default: [summary].
activityIdYesThe numeric activityId (from list_activities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that 'details' returns GPS/HR/power streams (a hint about payload size and content) and names the selectable sections, but it says nothing about permissions, error behavior, or response structure. Some value beyond the schema, but not rich behavioral context.

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?

Two compact sentences with zero waste. The core purpose is front-loaded, and the include enumeration follows immediately, making it easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with two well-described parameters, no output schema, and no annotations, the description covers purpose and section selection adequately. It lacks explicit return-shape or edge-case guidance, but nothing essential for correct invocation is missing.

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?

Schema coverage is 100%, so the schema already documents both parameters and the default for include. The description repeats the include options and adds a parenthetical clarifying 'details (GPS/HR/power streams),' which is helpful but marginal; the baseline of 3 is appropriate when the schema does most of the work.

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/resource pair: 'Data for a single activity by activityId,' which clearly distinguishes it from the list-oriented sibling list_activities. It does not explicitly name any siblings or contrast itself with them, so it falls short of the 5 anchor.

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?

Usage is implied by 'single activity by activityId' and the include-selection sentence, but the description never states when to call this instead of list_activities or other siblings, nor does it mention prerequisites or exclusions. Adequate but with a clear gap in explicit routing guidance.

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