Skip to main content
Glama
durely

durely insights

by durely
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Garmin activities

garmin_list_activities
Read-onlyIdempotent

Search and filter your Garmin activity history by date, sport, distance, duration, or name to retrieve compact, paginated summaries for training review.

Instructions

Search the user's Garmin activities (all history, from the local cache), newest first by default.

Returns one page of compact summaries plus the total number of matches: id, date, type, name, duration, distance, pace/speed, HR, power, elevation, training effect, training load, TSS/IF and VO2max where available, plus time in HR/power zones (JSON mode).

Examples:

  • "My runs this month" -> activity_type="running", start_date="2026-10-01"

  • "Longest rides ever" -> activity_type="cycling", sort_by="distance"

  • "Zwift sessions" -> activity_type="virtual_ride"

  • "Triathlon bike legs" -> include_multisport_legs=true, activity_type="road_biking"

The cache refreshes automatically when it's more than an hour old. Use garmin_get_activity for one activity's full details (splits, FTP, workout).

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum activities to return (1-100)
offsetNoNumber of activities to skip, for pagination
searchNoText to match in the activity name (case-insensitive)
sort_byNoSort fielddate
end_dateNoOnly activities on or before this local date, yyyy-MM-dd
sort_orderNodesc = newest/largest firstdesc
start_dateNoOnly activities on or after this local date, yyyy-MM-dd
activity_typeNoGarmin activity type or parent type. Parent types include their subtypes: running (trail_running, treadmill_running, track_running, virtual_run), cycling (road_biking, virtual_ride, indoor_cycling, mountain_biking, gravel_cycling), swimming (lap_swimming, open_water_swimming), walking, hiking, multi_sport, fitness_equipment (strength_training, indoor_cardio, indoor_rowing), racket_sports, water_sports, other.
max_distance_kmNoMaximum distance in km
min_distance_kmNoMinimum distance in km
response_formatNo'markdown' for readable text (default), 'json' for complete structured datamarkdown
max_duration_minNoMaximum duration in minutes
min_duration_minNoMinimum duration in minutes
include_multisport_legsNofalse (default): multisport activities appear once, as the parent. true: show their individual legs (swim/bike/run/transitions) instead of the parent, e.g. so triathlon bike legs count as cycling volume. Never double counts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the data comes from a local cache that auto-refreshes when older than an hour, and results are paged with a total match count. It stops short of describing pagination semantics for the total (whether total reflects filters), which keeps it from 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?

The core capability and scope are front-loaded in the first sentence, and the examples and sibling pointer are clearly delineated. It is somewhat long, but each element (return fields, examples, cache note, sibling routing) carries distinct information.

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?

For a 14-parameter read tool with no output schema, the description lists the returned summary fields and states the JSON/markdown response distinction, plus the paging model. Combined with 100% schema coverage, an agent has everything needed to select and call it correctly.

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 100%, so the baseline is 3, but the description adds value: the examples demonstrate how activity_type, start_date, sort_by, and include_multisport_legs combine for real intents, and they clarify the parent-type expansion and the 'never double counts' behavior of multisport legs in a way the schema terse descriptions do not.

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?

States a specific verb (search/list) and resource (Garmin activities) with scope ('all history, from the local cache') and ordering ('newest first by default'). It also names the sibling garmin_get_activity as the tool for a single activity's full details, so an agent can distinguish the two without opening either schema.

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?

Provides four concrete natural-language query examples mapped to specific parameter combinations, covering filtering by type/date, sorting, and multisport legs. It explicitly routes detail-seeking calls to garmin_get_activity and notes the cache-refresh condition that governs data freshness.

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