Garmin MCP by geekist.co

garmin_list_workouts

Read-onlyIdempotent

List a page of workouts saved in the connected Garmin account’s workout library. Returns workouts in workouts and requires a connected Garmin session. Use garmin_get_workout for one saved workout or garmin_get_activity_workouts for workouts linked to a completed 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_workouts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum workouts to request, 1–100; defaults to 20.
`start`	No	Zero-based starting offset; defaults to 0.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Maximum workouts to request, 1–100; defaults to 20."
```
- addedInput schema / properties / start / description
```
Added value: +"Zero-based starting offset; defaults to 0."
```
First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description adds the session prerequisite plus the fact that results arrive under the 'workouts' key. It also imposes a display obligation for serviceAnnouncements, which is genuine behavioral context. It stops short of describing pagination termination or error behavior, so it is not exhaustive.

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?

The purpose is front-loaded and each subsequent sentence serves routing or the announcement obligation. The parenthetical 'the independent service operator' is slightly wordy but supports the instruction to surface the messages, so it largely earns its place.

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 two-parameter read tool with full annotation coverage and no output schema, the description covers purpose, alternatives, auth precondition, and the return key. Only pagination completion and failure modes are left implicit, which is acceptable at this complexity.

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%, and both limit (1–100, default 20) and start (zero-based offset, default 0) are fully documented in the schema. The phrase 'a page of workouts' corroborates pagination but adds no syntax or cursor semantics beyond what the schema already provides, 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?

The first sentence gives a specific verb and resource ('List a page of workouts saved in the connected Garmin account's workout library') and names the return envelope. It then explicitly distinguishes itself from garmin_get_workout and garmin_get_activity_workouts, so the agent can differentiate without opening sibling schemas.

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?

It states the selection condition for the two closest alternatives: use garmin_get_workout for a single saved workout and garmin_get_activity_workouts for workouts tied to a completed activity, leaving this tool for browsing the library. There is also an implicit prerequisite (a connected Garmin session) that helps the agent decide whether it can call at all.

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?