Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by Sinfjell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_activities_by_date

Query Garmin Connect activity summaries for an inclusive date range by supplying start and end dates in YYYY-MM-DD format; returns a JSON array.

Instructions

List activities between two dates (inclusive).

start_date and end_date must be "YYYY-MM-DD". Returns a JSON array of activity summaries in the same shape as list_recent_activities.

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>",
      "end_date": "<end_date>"
    },
    "name": "list_activities_by_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose useful behavior — bounds are inclusive, dates must be 'YYYY-MM-DD', and the result is a JSON array of activity summaries — but says nothing about permissions, result size limits, ordering, or what an out-of-range or start-after-end input produces.

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 sentences, no filler, with the core action and the date-range constraint front-loaded ahead of the return-shape note. Every clause carries information an agent needs.

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?

For a two-parameter read tool this is largely sufficient: format, inclusivity, and the return shape are all covered, and an output schema exists so return values need no elaboration. The absence of annotations means some behavioral detail (permissions, limits, ordering) is left undisclosed, keeping it short of a 5.

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

Parameters4/5

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

Schema coverage is 0% (both properties carry only titles 'Start Date' and 'End Date'), so the description must compensate, and it does: it fixes the exact 'YYYY-MM-DD' format and states that both endpoints are inclusive. Minor gaps remain, such as whether the range is normalized or ordering enforced, but the essential meaning is added beyond the schema.

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 description opens with a specific verb and resource, 'List activities', and narrows scope with 'between two dates (inclusive)', which is enough to distinguish it from list_recent_activities in practice. It stops short of an explicit 'this is the ranged-listing tool, not the recent-feed tool' statement, but the intent is unambiguous.

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 only implied: the date-range framing signals 'use this for a bounded historical window', and the reference to list_recent_activities hints at the alternative for unfiltered recent data. There is no explicit when-to-use or when-not-to-use guidance, nor any statement about what happens with an empty or reversed range.

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