Skip to main content
Glama

Garmin Activities

garmin_list_activities
Read-onlyIdempotent

Retrieve a list of recent Garmin activities with optional filters for date range, activity type, and pagination. Adjust privacy modes to get summary, structured, or raw data.

Instructions

List recent Garmin activities. Supports pagination, optional date filters and privacy modes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoGarmin page number.
afterNoOnly return activities after this time. Used as Garmin startDate when supported.
limitNoGarmin page size.
beforeNoOnly return activities before this time. Used as Garmin endDate when supported.
all_pagesNoFetch multiple pages up to max_pages.
max_pagesNoMaximum pages to fetch when all_pages is true.
privacy_modeNoOptional per-call privacy override. Defaults to GARMIN_PRIVACY_MODE or structured. raw returns upstream Garmin JSON. summary removes GPS/map details.
activity_typeNoOptional Garmin activity type filter, e.g. running, cycling, walking.
response_formatNomarkdown
explicit_user_intentNoRequired true when privacy_mode=raw or include_gps=true (agent escalation of redaction).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
recordsYes
endpointYes
has_moreYes
next_pageNo
privacy_modeYes
pages_fetchedYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context about pagination, date filters, and privacy modes, which are beyond what annotations provide. No contradictions.

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?

The description is a single sentence that is front-loaded with the action ('List recent Garmin activities') and efficiently lists key capabilities. No wasted words.

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?

For a tool with 10 parameters and an output schema, the description covers core features (listing, pagination, date filters, privacy) but omits mention of activity_type, explicit_user_intent, and the environment variable GARMIN_PRIVACY_MODE. It is adequate but not fully comprehensive.

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?

Schema description coverage is 90%, so the schema already documents most parameters. The description summarizes functionality (pagination, date filters, privacy) but does not add significant new meaning beyond the schema's parameter descriptions.

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 clearly states the tool lists recent Garmin activities, distinguishing it from siblings like garmin_get_activity (single activity) and garmin_get_activity_details (details for one). It specifies supported features (pagination, date filters, privacy modes), making it 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?

The description implies when to use this tool (for multiple activities) but does not explicitly contrast with alternatives like garmin_get_activity or garmin_daily_summary. No exclusions or when-not-to-use guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/garmin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server