Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by Sinfjell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_recent_activities

Retrieve Garmin activity summaries in reverse chronological order, including type, distance, duration, heart rate, and pace; set a limit to control result count.

Instructions

List the most recent Garmin activities, newest first.

Returns a JSON array of activity summaries with: id (use with get_activity_details), date (YYYY-MM-DDTHH:MM local time), type (e.g. "running", "cycling"), name, distance_km, duration_min, avg_hr, and pace_min_per_km. limit caps how many activities come back (default 10).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it discloses ordering (newest first), a default limit of 10, and the shape of the returned summaries. It does not state that the call is read-only, whether data is available offline or requires auth, or what happens when limit exceeds available activities. It is adequate but does not fully cover behavior for an unannotated tool.

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?

Two short blocks: a front-loaded purpose sentence followed by a compact field inventory. No filler, and the ordering and default are stated up front rather than buried.

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 one-parameter read tool this is essentially complete: purpose, ordering, default, and return fields are all present. Because an output schema exists, the field enumeration is somewhat redundant, but nothing an agent needs in order to call it correctly is missing.

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 compensate: it does, explaining that `limit` caps how many activities come back and that the default is 10. That is the essential semantics an agent needs for the only parameter, though it does not mention valid ranges or an upper bound.

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 opens with a specific verb and resource, 'List the most recent Garmin activities,' and adds a deterministic ordering ('newest first'), so the agent knows exactly what it retrieves. It does not, however, distinguish itself from the sibling list_activities_by_date, which an agent could easily confuse with it.

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?

Usage is only implied by 'most recent' and the ordering constraint; there is no explicit when-to-use statement or when-not statement. The one routing hint is embedded in the return-field list ('id (use with get_activity_details)'), which does point the agent to a sibling, but the alternative list_activities_by_date is never mentioned.

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