garmin-mcp

Overview Schema Source Related Servers Discussions Admin

list_activities

Read-onlyIdempotent

Retrieve completed Garmin activities within a date range, with optional activity type filter, returning compact planning metrics without GPS or owner details.

Instructions

List completed Garmin activities in an inclusive YYYY-MM-DD date range.

Returns compact planning metrics and omits GPS coordinates and owner details. activity_type is an optional Garmin type key such as running or cycling.

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": {
      "start_date": "<start_date>"
    },
    "name": "list_activities"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`end_date`	No
`start_date`	Yes
`activity_type`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so no duplication needed. The description adds useful behavioral context beyond annotations: it returns compact metrics, omits GPS and owner details, and uses an inclusive date range. This adds value without contradiction.

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 concise sentences front-load the purpose and add key details. No fluff, every word earns its place. The structure is clear and efficient.

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?

Given the availability of an output schema and rich annotations, the description is adequate for a list tool. It covers the core purpose, date inclusivity, and notable omissions. However, it could be more complete by mentioning pagination or limit behavior, and by explicitly contrasting with sibling detail tools.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It explains the date range inclusivity and gives an example for activity_type, but does not mention the 'limit' parameter at all, and implicitly treats start_date/end_date as a pair without specifying which are required. Over half of the parameters remain unexplained.

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 it lists completed Garmin activities within an inclusive date range. It distinguishes itself from siblings like get_activity_summary or get_activity_splits by focusing on listing rather than details, and from list_workouts by specifying 'activities' instead of 'workouts'.

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 usage (for a high-level list of activities) but does not explicitly mention alternatives or when not to use this tool. Comments about omitting GPS and owner details hint at limitations but do not direct the user to sibling tools like get_activity_summary for richer data.

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

Deploy Server