Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_activities_by_date

Read-only

Retrieve Garmin Connect activities between two dates, with optional activity type and sort order filters, to review workouts and training history.

Instructions

Return activities between two dates, optionally filtered by type. :param startdate: String in the format YYYY-MM-DD :param enddate: (Optional) String in the format YYYY-MM-DD :param activitytype: (Optional) Type of activity you are searching Possible values are [cycling, running, swimming, multi_sport, fitness_equipment, hiking, walking, other] :param sortorder: (Optional) sorting direction. By default, Garmin uses descending order by startLocal field. Use "asc" to get activities from oldest to newest. :return: list of JSON activities. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)

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": {
      "startdate": "<startdate>"
    },
    "name": "get_activities_by_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
enddateNo
sortorderNo
startdateYes
activitytypeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already state readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond that: default sort is descending by startLocal, 'asc' reverses to oldest-first, and it names the Garmin Connect source as read-only. It does not discuss pagination or result limits, which leaves a modest gap for a list-returning tool.

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 in the first sentence, and the parameter notes are grouped efficiently. The Sphinx-style ':param:' formatting is a bit mechanical, and the YYYY-MM-DD format is repeated at the end, but there is no serious 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?

With an output schema present, the description does not need to explain return values in depth, and it still notes that the return is a list of JSON activities. It covers date format, filter values, and sort behavior. Pagination or result-limit behavior is the main missing piece for a date-range listing tool.

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

Parameters5/5

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

Schema description coverage is 0%, so this description carries the full burden and does so well. It documents all four parameters: startdate format and implied requiredness, optional enddate format, optional activitytype with the full allowed value list, and optional sortorder with its default behavior and 'asc' semantics.

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?

The first sentence gives a specific verb and resource: return activities between two dates, optionally filtered by type. It is clear enough to separate from daily metric tools, but it does not explicitly distinguish itself from close siblings such as get_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?

Usage is implied by the date-range framing: use this when you need activities between two dates, optionally by type. However, the description gives no explicit when-to-use guidance, no exclusions, and no comparison to sibling tools like get_activities or get_last_activity.

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