Skip to main content
Glama
sedoglia

Garmin Connect MCP Server

by sedoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Activities by Date

get_activities_by_date
Read-only

Retrieve Garmin Connect activities within a specified date range, with optional activity type filter. Summarizes each activity to review training history or analyze performance over any period.

Instructions

Get all activities within a date range, optionally filtered by type. Each one is summarised the same way list_recent_activities summarises them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of activities to list (1-200, default 100). The response says when the range holds more; count_activities gives the total without listing them, and get_progress_summary or analyze_training_period aggregate the whole range.
endDateNoEnd date in YYYY-MM-DD format
sortOrderNoSort order: asc (oldest first) or desc (newest first, default)
startDateYesStart date in YYYY-MM-DD format (required)
activityTypeNoFilter by activity type: running, cycling, swimming, hiking, walking, fitness_equipment, etc. A sub type such as strength_training or trail_running is accepted too — Garmin filters by top-level type only, so it is queried under its parent and narrowed back down here. get_activity_types lists every key.
includeDetailsNoReturn every field the activity list service sends rather than the summary (default false). Roughly ten times larger; a range holding more than about 25 activities will not fit in a response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.5.8
    • changedInput schema / properties / activityType / description
      Previous value: -"Filter by activity type: running, cycling, swimming, hiking, walking, etc."New value: +"Filter by activity type: running, cycling, swimming, hiking, walking, fitness_equipment, etc. A sub type such as strength_training or trail_running is accepted too — Garmin filters by top-level type only, so it is queried under its parent and narrowed back down here. get_activity_types lists every key."
  2. Changed2 schema fields changedv4.5.7
    • addedInput schema / properties / includeDetails
      Added value: +{
+  "description": "Return every field the activity list service sends rather than the summary (default false). Roughly ten times larger; a range holding more than about 25 activities will not fit in a response.",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum number of activities to list (1-200, default 100). The response says when the range holds more; count_activities gives the total without listing them, and get_progress_summary or analyze_training_period aggregate the whole range.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "number"
+}
  3. First observedv4.3.0

TDQS

A4/5.0
Behavior4/5

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

Read-only behavior is already covered by readOnlyHint=true, so the description does not need to restate that. It adds behavioral context by explaining that each activity is returned as a summary in the same format as list_recent_activities, which tells the agent what kind of response to expect. It does not deeply discuss pagination or the includeDetails override, but those are documented in the schema.

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?

The description is two concise sentences with no filler. The core scope is front-loaded, and the second sentence adds the key output-format detail by referencing a sibling tool.

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 rich schema descriptions and read-only annotation, the main description covers the most important missing piece: the response is a set of summaries whose shape matches list_recent_activities. It does not enumerate return fields or edge cases, but the schema covers parameter behavior and the sibling reference provides output format context.

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%, so the schema already explains every parameter, including limit, date formats, sort order, activityType, and includeDetails. The description only adds 'optionally filtered by type', which reinforces the activityType parameter but does not materially improve on the schema's descriptions. Baseline 3 is appropriate.

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 states a specific verb and resource ('Get all activities') with scope ('within a date range, optionally filtered by type') and clarifies output shape by referencing list_recent_activities summaries. This makes it easy to distinguish from sibling tools such as list_recent_activities or count_activities.

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 the tool is for date-range activity listing, and it references list_recent_activities for summary format, but it does not explicitly say when to prefer this tool over alternatives like count_activities or analyze_training_period. If consideration is limited to the main description, the usage guidance is mostly implicit rather than explicit.

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

Deploy Server

Other Tools