garmin-connect-mcp

by jharkebusch

Overview Schema Source Related Servers Discussions Admin

Python

Local

list_workouts

List saved workout plans from Garmin Connect. Use the optional limit parameter to control how many plans are returned.

Instructions

List the saved workout plans in Garmin Connect.

Args: limit: Most workouts to list. Defaults to 25.

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": "list_workouts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It does not state that the operation is read-only, whether authentication is required, or the structure of the response (e.g., pagination). The description adds little beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but includes an unnecessary 'Args' section that merely echoes the schema. While not verbose, it is not optimally structured (e.g., missing a clear purpose statement beyond the first line). It could be more front-loaded and concise.

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

Completeness2/5

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

The tool has an output schema (not shown), but the description does not mention what the list contains (e.g., workout names, IDs) or any ordering, sorting, or filtering behavior beyond the limit. For a list tool with only one parameter, completeness is minimal; an agent would lack key context for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning the description should compensate by explaining the `limit` parameter's meaning, constraints, or behavior. It merely restates the schema defaults with 'Most workouts to list. Defaults to 25.' – no additional semantics or constraints are provided.

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 description clearly states the action ('list') and the resource ('saved workout plans in Garmin Connect'). It distinguishes itself from sibling tools like `get_workout` and `get_scheduled_workouts` by specifying 'plans' (plural) and the scope 'saved'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as `get_scheduled_workouts` or `get_workout`. There is no mention of prerequisites, default behavior, or limitations, leaving the agent without context for selection.

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