Skip to main content
Glama

get_activities

Read-only

Retrieve a paginated list of Garmin Connect activities, newest first, to browse large activity histories or complement date-range queries.

Instructions

Get activities with pagination support.

    Retrieves a paginated list of activities ordered newest-first. Use this
    for browsing through large activity lists when you do not need to filter
    by date range, or as a complement to get_activities_by_date.

    Each activity includes an event_type field. Common values: "race",
    "training", "uncategorized" (no event type set by the user — common for
    Peloton imports and untagged runs). Filter for races with
    event_type == "race" rather than excluding "training", as many non-race
    activities appear as "uncategorized" rather than "training".

    Args:
        start: Starting index (default 0)
        limit: Maximum number of activities to return (default 20, max 100)
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds value beyond that with the newest-first ordering and the semantics of the event_type field, including what 'uncategorized' typically means. It does not mention rate limits or response shape beyond the one field, which keeps it short of a 5.

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?

Purpose and usage are front-loaded, and the event_type paragraph carries real domain knowledge rather than filler. The trailing Args block partially duplicates schema defaults, but it also carries the max-100 constraint, so it earns most of its space.

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-only list tool with no output schema, the description covers ordering, paging bounds, and the most important returned field, which is enough to call it correctly. It does not sketch the other activity fields an agent will receive, a minor gap given no output schema exists.

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 description coverage is 0%, so the description must carry the burden, and it does: 'start' is defined as a starting index and 'limit' gets a default of 20 and a hard maximum of 100 that the schema does not express. It stops short of explaining how to page (e.g., increment start by limit), which would have made it a 5.

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 ('Retrieves a paginated list of activities ordered newest-first') and immediately distinguishes itself from the sibling get_activities_by_date. An agent can tell from the text alone whether this is the unfiltered browse tool or the date-scoped one.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use condition ('browsing through large activity lists when you do not need to filter by date range') and names the alternative tool it complements. It also adds a filtering rule of thumb for event_type, telling the agent to match 'race' rather than exclude 'training' — concrete guidance that prevents a common mistake.

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