mcp-garmin-connect

Overview Schema Source Related Servers Discussions Admin

get_recent_activities

Retrieve recent Garmin Connect activities with sport-aware summary fields for training review. Query a specific start/end date window or use a day lookback to analyze past workouts.

Instructions

Recent Garmin activities with normalized sport-aware summary fields.

Pass start_date/end_date for a specific historical window (both inclusive); otherwise the days lookback is used. Explicit dates make a past window queryable without pulling every newer activity first.

Input Schema

Name	Required	Description
`days`	No	How many days back to include. Ignored when start_date is given.
`limit`	No	Maximum number of activities to return.
`end_date`	No	YYYY-MM-DD. Window end, inclusive. Defaults to today.
`start_date`	No	YYYY-MM-DD. Explicit window start (overrides days).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.4.0Oct 31, 2026

changedInput schema / properties / days / description

Previous value: -"How many days back to include."New value: +"How many days back to include. Ignored when start_date is given."

addedInput schema / properties / end_date

Added value: +{
+  "default": "",
+  "description": "YYYY-MM-DD. Window end, inclusive. Defaults to today.",
+  "title": "End Date",
+  "type": "string"
+}

addedInput schema / properties / start_date

Added value: +{
+  "default": "",
+  "description": "YYYY-MM-DD. Explicit window start (overrides days).",
+  "title": "Start Date",
+  "type": "string"
+}

Changed6 schema fields changedv0.2.0Oct 3, 2026
- addedInput schema / properties / days / description
```
Added value: +"How many days back to include."
```
- addedInput schema / properties / days / maximum
```
Added value: +365
```
- addedInput schema / properties / days / minimum
```
Added value: +1
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum number of activities to return."
```
- addedInput schema / properties / limit / maximum
```
Added value: +200
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
First observedv0.1.0Aug 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations present, the description does carry the full burden, and it does disclose two useful traits: results are summary-level rather than full activity detail, and explicit dates override the lookback. It says nothing about ordering, whether limit truncates the newest or oldest activities, or the read-only nature of the call.

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?

Three short sentences with the core purpose front-loaded and the window logic second; nothing is padding. The window-timing sentence partially duplicates the schema descriptions, which is the only waste.

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?

All four parameters are optional and fully documented in the schema, and an output schema exists, so return values need no explanation. The one real gap is the absence of any routing signal among the many sibling activity/summary tools.

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%, including the precedence rule ('Ignored when start_date is given'), so the baseline is 3. The description restates that same precedence and the inclusive-window semantics, adding no format or interaction details the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource ('Recent Garmin activities') and the shape of the return ('normalized sport-aware summary fields'), so an agent knows this is a list-of-activities tool rather than a per-activity detail tool. It does not, however, distinguish itself from summary-oriented siblings such as get_running_summary or get_monthly_running_stats.

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 explains the date-window mechanics ('Pass start_date/end_date ... otherwise the days lookback is used'), but that is parameter guidance rather than tool-selection guidance. It never says when to reach for this tool instead of get_activity_detail, get_running_summary, or get_recent_load, so the agent must infer that from the name alone.

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