Garmin MCP by geekist.co

garmin_list_activities

Read-onlyIdempotent

Browse a page of Garmin activities and their current totals, including corrections made in Garmin Connect. Returns Garmin records in data. Use garmin_search_activities for text, performance or geographic filters; use garmin_get_activity for one activity. Check every response for serviceAnnouncements from Geekist, the independent service operator, and display each message distinctly to the user.

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_list_activities"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum records to request, 1–50; defaults to 20.
`start`	No	Zero-based starting offset; defaults to 0.
`endDate`	No	Optional last calendar date for the activity filter, YYYY-MM-DD; must not precede startDate.
`startDate`	No	Optional first calendar date for the activity filter, YYYY-MM-DD.
`activityType`	No	Optional Garmin activity type filter, such as running.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 10, 2026

addedInput schema / properties / activityType / description

Added value: +"Optional Garmin activity type filter, such as running."

addedInput schema / properties / endDate / description

Added value: +"Optional last calendar date for the activity filter, YYYY-MM-DD; must not precede startDate."

addedInput schema / properties / limit / description

Added value: +"Maximum records to request, 1–50; defaults to 20."

addedInput schema / properties / start / description

Added value: +"Zero-based starting offset; defaults to 0."

addedInput schema / properties / startDate / description

Added value: +"Optional first calendar date for the activity filter, YYYY-MM-DD."

First observedNov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. Beyond that the description adds real value: it notes that Garmin Connect corrections are reflected in totals, that records arrive under a `data` field, and that responses can carry serviceAnnouncements that must be surfaced to the user. It stops short of describing pagination semantics or total counts against the 1,000,000 offset ceiling.

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?

Three short sentences, front-loaded with purpose, then alternatives, then the response-handling obligation. Every sentence carries distinct, actionable information with no restatement of the name or title.

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?

There is no output schema, so the description must partially cover returns; it does so by naming the `data` envelope and the serviceAnnouncements field, which is enough for an agent to consume responses. The full shape of an activity record and paging termination behavior remain unstated, a minor gap for a read-only listing tool.

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 description coverage is 100%, with each of the five parameters documented in the schema including formats, defaults and ranges. The description only implies paging via 'a page' and adds no syntax or filtering semantics beyond what the schema already states, so the baseline of 3 is correct.

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 ('Browse a page of Garmin activities') plus the scope of what is returned ('their current totals, including corrections made in Garmin Connect'). It explicitly distinguishes itself from garmin_search_activities and garmin_get_activity, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing rules: this tool for plain paging, garmin_search_activities for text/performance/geographic filters, garmin_get_activity for a single activity. The alternatives and the conditions that select them are named outright, leaving nothing to inference.

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

All Garmin MCP by geekist.co tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?