Skip to main content
Glama
Sign In

Garmin MCP by geekist.co

by io.github.theGeekist
OverviewDiscussionsAdmin

garmin_get_activity_fit_file

Read-onlyIdempotent

Download Garmin’s original activity file response as ordered base64-encoded byte chunks, preserving its ZIP wrapper if supplied. The format is zip, fit or unknown. Decode each chunk and concatenate in order. On subsequent calls pass nextOffset and the first response’s sha256; the checksum is required when offset is greater than zero. Restart if the file changes. The recorded file is separate from current corrected Garmin Connect totals, available through garmin_get_activity. 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_fit_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum bytes in this chunk, 1–196608; defaults to 196608.
offsetNoZero-based byte offset in the original download. Pass the previous response’s nextOffset.
sha256NoSHA-256 from the first response; required when offset is greater than zero.
activityIdYesGarmin 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.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description adds substantive behavior beyond them: chunked retrieval with a checksum gate at offset > 0, invalidation when the file changes, and a mandate to surface serviceAnnouncements from the third-party operator. These are operational constraints an agent could not infer from the annotations or schema.

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 the core action and the chunk/decode instructions, with the file-vs-totals distinction placed where it prevents a wrong tool choice. Slightly dense in places ('The format is zip, fit or unknown') and the serviceAnnouncements requirement, while policy-relevant, reads as appended boilerplate.

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?

With no output schema, the description carries the full burden of describing the response and does so: ordered base64 chunks, nextOffset, sha256, format classification, and serviceAnnouncements. Nothing an agent needs to execute the paging protocol 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 coverage is 100%, so the baseline is 3, but the description goes past the field text by explaining the cross-call relationship — sha256 comes from the first response and is mandatory once offset is positive, and chunks must be concatenated in offset order. It does not add much new on limit beyond the schema's own byte-range documentation.

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 — downloading Garmin's original activity file as ordered base64 chunks with the ZIP wrapper preserved — and explicitly contrasts it with garmin_get_activity's corrected totals. An agent can distinguish it from the many sibling activity readers 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 Guidelines5/5

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

Names the alternative (garmin_get_activity for corrected totals) and states the condition that selects it (when you need the original recorded file). Also prescribes the multi-call protocol: decode and concatenate, pass nextOffset plus the first response's sha256, and restart if the file changes.

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 toolsInspect
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