Skip to main content
Glama

get_activity_laps

Retrieves individual laps or auto-kilometer splits for a Garmin activity, returning per-lap distance, durations, pace, heart rate, power, cadence, intensity, and elevation data for split analysis.

Instructions

Get the individual laps of an activity (intervals or auto-km splits).

activity_id is the numeric id from list_recent_activities. Returns a JSON object with "lap_count" and a "laps" array, one entry per real Garmin lap: lap number, distance_m, the three durations (elapsed_time_s, timer_time_s, moving_time_s), pace_min_per_km, avg/max HR, avg/max power, avg_run_cadence, "intensity" (e.g. WARMUP/ACTIVE/REST — the interval structure), and elevation gain/loss. Use this instead of get_activity_details when you need per-lap threshold or split analysis. GPS start/end coordinates are omitted by default; pass include_gps=true to include them.

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": {
      "activity_id": "<activity_id>"
    },
    "name": "get_activity_laps"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYes
include_gpsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so well: it states the return shape (lap_count plus laps array with named fields), discloses the default of omitting GPS coordinates, and explains how to opt in via include_gps. It doesn't state rate limits or that this is a read-only call, but the read nature is implicit in 'Get'.

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?

Front-loaded with purpose, then usage routing, then the return contents, then the GPS caveat. The middle sentence enumerating lap fields is long but useful given the 0% schema coverage; nothing is wasted.

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?

An output schema exists, so the detailed return enumeration is partly redundant, but it helps an agent decide between laps and details. Combined with the id provenance and GPS flag, the definition is complete for a 2-parameter read tool.

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 explains activity_id's provenance and include_gps's default and effect. There is a minor mismatch: the schema types activity_id as a string while the description calls it a 'numeric id', which could confuse an agent on formatting.

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 and resource ('Get the individual laps of an activity') and immediately clarifies the two modes (intervals or auto-km splits), which an agent can distinguish from get_activity_details and list_recent_activities without opening the schema.

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

Usage Guidelines4/5

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

Gives an explicit alternative:'Use this instead of get_activity_details when you need per-lap threshold or split analysis,' and tells where activity_id comes from (list_recent_activities). The closely related sibling get_activity_intervals is not addressed, leaving a small routing ambiguity.

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