Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by sasha-sup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

garmin_activity

Read-onlyIdempotent

Retrieve a full workout summary by activity ID, including all Garmin-computed measurements such as temperature, cadence, power, and training effect messages.

Instructions

Full summary of one workout by activity_id (from garmin_activities): all measurements Garmin computed, including temperature, cadence, power, training effect messages.

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": {
      "activity_id": "<activity_id>"
    },
    "name": "garmin_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYesActivity ID from garmin_activities.

Output Schema

NameRequiredDescriptionDefault
nameYes
typeYes
unitsYes
summaryYes
event_typeNo
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is fully covered. The description adds that results include Garmin-computed measurements such as temperature, cadence, power, and training effect messages, but an output schema exists, so return content is already documented elsewhere. Little behavioral context (e.g., failure modes for a bad ID, latency) is added.

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?

A single front-loaded sentence with no filler; the resource, key, provenance, and returned content are all delivered up front with nothing that could be cut.

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 one-parameter read-only tool with an output schema and full annotation coverage, the description says enough to call it correctly and know what comes back. Only the explicit follow-on relationship to garmin_activities and any error behavior are left implicit.

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% and the single activity_id parameter is fully described in the schema. The description only adds provenance ('from garmin_activities'), which is mildly helpful for obtaining a valid ID but does not add format or validity semantics beyond the schema.

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?

States a specific verb and resource: 'Full summary of one workout by activity_id,' and the parenthetical '(from garmin_activities)' signals it is the detail counterpart to the list sibling. An agent can distinguish it from garmin_activities without opening the schema, though it never explicitly says 'use this after garmin_activities to drill into a single 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 description implies the workflow by noting the ID comes from garmin_activities, which is useful routing. However, it gives no explicit when-to-use vs. when-not guidance and names no alternative tools (e.g., garmin_trends or garmin_daily_summary) for aggregate versus per-activity views.

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