garminconnect-js

get_activities_by_date

Read-only

Retrieve Garmin activities between two dates, optionally filtered by activity type. Handles pagination automatically to fetch all results.

Instructions

Every activity between two dates, optionally filtered by activity type. Pages through the results internally. Paginates internally: fetches fixed pages of 20, incrementing start by 20, until an empty page (normal end) or 2000 pages without one (throws GarminError).

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

Name	Required	Description
`enddate`	No	Calendar date, YYYY-MM-DD (UTC)
`sortorder`	No
`startdate`	Yes	Calendar date, YYYY-MM-DD (UTC)
`activitytype`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, so safety is covered, yet the description adds real behavioral context the agent could not otherwise know: fixed 20-item pages incremented via `start`, termination on an empty page, and a hard cap of 2000 pages before throwing GarminError. That failure mode is genuinely useful for a client.

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 core scope is front-loaded and the pagination mechanics are useful. The two opening pagination sentences ('Pages through the results internally. Paginates internally: ...') restate the same fact, a small redundancy in an otherwise tight description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should say more about what each activity record contains and how the result set is shaped, and it leaves sortorder and enddate semantics unexplained. It does cover the risky part (internal pagination and its error condition) well.

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?

The description conveys that startdate/enddate form the range and that activitytype is an optional filter, but sortorder is never explained and enddate's optionality/default is not stated. With 50% schema coverage, the schema documents only the two date formats, so the description partially compensates but leaves gaps.

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 gives a specific verb and resource ('Every activity between two dates') plus an optional filter by activity type, so the operation is clear. It does not, however, distinguish itself from close siblings such as get_activities, get_activities_for_date, or get_last_activity, which an agent must disambiguate by name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance or mention of alternatives, despite many overlapping activity-retrieval siblings in the toolset. The only routing signal is the implied date-range scope.

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

Deploy Server