Skip to main content
Glama

get_activities_by_date

Read-only

Retrieve Garmin Connect activities for a date range with optional activity-type filtering and pagination to handle large histories in manageable pages.

Instructions

Get activities between specified dates with pagination support.

    For accounts with large activity histories, broad date ranges can return
    thousands of activities in a single response. Use page and page_size to
    retrieve activities in manageable chunks and avoid "result too large" errors.
    Activities are ordered newest-first.

    Pagination: when has_more is true the response includes next_page — pass
    that value as page on the next call to retrieve the following page. Repeat
    until has_more is false.

    Note: total_count for a date range is not available from the Garmin API
    without fetching all results. Use has_more / next_page to walk pages.

    Each activity includes an event_type field with values such as:
      - "race"          — explicitly tagged as a race by the user
      - "training"      — explicitly tagged as a training activity
      - "uncategorized" — no event type set; common for Peloton imports and
                          untagged outdoor runs. Distinct from "training":
                          filter for races with event_type == "race" rather
                          than excluding "training", since many non-race
                          activities appear as "uncategorized" not "training"
      - field absent    — API returned no eventType for this activity; not
                          observed in practice in any activity back to 2012
                          (oldest activities sampled on this account)

    Args:
        start_date: Start date in YYYY-MM-DD format
        end_date: End date in YYYY-MM-DD format
        activity_type: Optional activity type filter (e.g., cycling, running, swimming)
        page: Zero-based page number (default 0)
        page_size: Number of activities per page, max 200 (default 100)
    

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": "get_activities_by_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
end_dateYes
page_sizeNo
start_dateYes
activity_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: results are newest-first, pagination uses has_more and next_page, total_count is unavailable without fetching all pages, and it explains event_type values including the distinction between races, training, and uncategorized activities. This is rich context for correct invocation.

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 description is front-loaded and well structured, with separate sections for pagination and event_type semantics. It is somewhat verbose, especially the detailed note about absent event_type fields, but most of the detail is operationally useful.

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

Completeness5/5

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

Given five parameters, no schema descriptions, and no output schema, the definition covers the essentials: date filtering, pagination mechanics, ordering, response-field caveats, and the event_type field. An agent has enough information to call and paginate this tool correctly.

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?

Although the input schema has 0% description coverage, the description documents every parameter: date formats, optional activity_type filter examples, zero-based page numbering, and page_size maximum with defaults. It fully compensates for the bare 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 states a specific verb and resource: get activities between specified dates, with pagination support. It is clear what the tool returns and its date-scoped focus, but it does not explicitly distinguish itself from sibling tools such as get_activities or get_activities_fordate.

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?

It gives useful operational guidance for pagination and warns that broad date ranges may return thousands of activities, so callers should use page and page_size. However, it does not say when to choose this tool over alternatives like get_activities or get_activities_fordate.

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