Garmin MCP by geekist.co

garmin_get_activity_laps

Read-onlyIdempotent

Read decoded FIT lap records and device information alongside the current Garmin Connect activity. Recorded lap values are in laps; current activity totals, including later corrections, are in activity. Use garmin_get_activity_samples for individual sensor records. Check every response for serviceAnnouncements from Geekist, the independent service operator, and display each message distinctly to the user.

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": {
      "activityId": "<activityId>"
    },
    "name": "garmin_get_activity_laps"
  }
}

Input Schema

Name	Required	Description	Default
`activityId`	Yes	Garmin activity ID as a positive decimal string; obtain it from garmin_list_activities or garmin_search_activities.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

addedInput schema / properties / activityId / description

Added value: +"Garmin activity ID as a positive decimal string; obtain it from garmin_list_activities or garmin_search_activities."

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds genuine behavioral context beyond that: laps carry as-recorded values while activity totals may include later corrections, and responses may include serviceAnnouncements from the independent operator that must be surfaced to the user.

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?

Three short sentences, front-loaded with the primary purpose and the laps-versus-totals distinction. The final sentence about serviceAnnouncements is operationally useful but slightly displaced from the main purpose statement.

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?

With no output schema, the description still indicates what comes back: lap records, device information, and an activity block with corrected totals. For a one-parameter read tool this is close to sufficient, though it does not describe lap record shape or ordering.

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 coverage is 100% for the single activityId parameter, and the schema already documents its format and where to obtain it. The description adds no further meaning about the identifier, which is acceptable given the schema does the full job here.

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: reading decoded FIT lap records and device information for a Garmin Connect activity. It goes further by distinguishing lap-level values ('in laps') from corrected activity totals ('in activity'), which no sibling name alone would convey.

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?

It explicitly routes the agent to garmin_get_activity_samples when individual sensor records are wanted, establishing the main selection boundary among the per-activity siblings. It does not address when to prefer garmin_get_activity or garmin_get_activity_details, so the guidance is clear but not exhaustive.

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

All Garmin MCP by geekist.co tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?