Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by wiande00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

garmin_activities

Read-only

Lists Garmin Connect activities newest first with type, date, distance, duration, pace or speed, heart rate, training load, and effect; pass an activity ID to view details.

Instructions

List activities, newest first: id, type, start time, distance, time, pace or speed, heart rate, training load and effect. Pass an id to garmin_activity for detail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "garmin_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 0
limitNoPer page, 1-100. 0 returns only the total count.
end_dateNoLast day, inclusive. Default today.
start_dateNoFirst day (YYYY-MM-DD/today/yesterday). Omit both dates for the latest.
activity_typeNoType key, e.g. running, cycling, walking, strength_training

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are ordered newest first and the payload includes a named set of metrics, which matters because there is no output schema. It does not mention pagination behavior, but the schema covers that.

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 sentences, both earning their place: the first front-loads the operation and the return payload, the second handles routing. No filler or restatement of the name.

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 read-only list tool with no output schema, describing the returned fields is the key missing piece and the description supplies it. Pagination, date defaults, and type keys are fully handled by the schema, leaving only minor gaps such as result-set size or total-count behavior.

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 parameter descriptions are unusually rich (page from 0, limit 1-100 with the 0-returns-count special case, date formats, activity type keys). The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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 and resource ("List activities") plus ordering ("newest first") and the exact fields returned, so an agent knows precisely what comes back. It also names the sibling garmin_activity for single-activity detail, distinguishing itself from that tool without requiring schema inspection.

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?

Explicitly routes the agent to garmin_activity when a specific activity id is known, which is the main fork among siblings. It does not itself discuss date-filtering versus latest-only behavior, but that guidance is present in the schema's start_date description, so the gap is minor.

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