Garmin MCP by geekist.co

garmin_read_data

Read-onlyIdempotent

Read Garmin records from your connected account using a documented Personal API GET endpoint and its supported arguments. Use garmin_data_catalog to find allowed endpoints and fields. Each listed endpoint is also available as a dedicated read tool. 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": {
      "endpoint": "<endpoint>"
    },
    "name": "garmin_read_data"
  }
}

Input Schema

Name	Required	Description
`query`	No	Supported query parameters for the selected endpoint; omit when none are needed.
`endpoint`	Yes	Allowed endpoint path from garmin_data_catalog, including any parameter placeholders.
`pathParams`	No	Values for the endpoint’s named path placeholders; omit when none are required.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 10, 2026

addedInput schema / properties / endpoint / description

Added value: +"Allowed endpoint path from garmin_data_catalog, including any parameter placeholders."

addedInput schema / properties / pathParams / description

Added value: +"Values for the endpoint’s named path placeholders; omit when none are required."

addedInput schema / properties / query / description

Added value: +"Supported query parameters for the selected endpoint; omit when none are needed."

First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world semantics, so the description is not obligated to restate safety. It still adds non-obvious behavior: responses may carry serviceAnnouncements that must be surfaced distinctly, and the service is operated by a third party (Geekist). It omits pagination, rate limits, and error behavior, keeping it below a 5.

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 sentences, front-loaded with the core action, then discovery guidance, then the response-handling obligation. The operator attribution ('from Geekist, the independent service operator') is the only mildly padded clause, but it carries disclosure value.

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?

With no output schema, the description is the only source for return-value guidance, and it covers just one aspect (serviceAnnouncements) while saying nothing about response shape, paging, or errors for a 26-endpoint generic reader. Pointing to garmin_data_catalog offsets some of that gap but leaves the agent guessing on result structure.

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 100% and the endpoint enum, query, and pathParams objects are each documented in-schema, so the baseline applies. The description only says 'documented endpoint and its supported arguments' without adding format or constraint detail beyond the schema, which is adequate but not additive.

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?

States a specific verb and resource: read Garmin records via a documented Personal API GET endpoint with supported arguments. It also positions itself against siblings by noting each listed endpoint has a dedicated read tool, so an agent can tell this is the generic escape hatch rather than a specialized reader.

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?

It gives a useful prerequisite — consult garmin_data_catalog to discover allowed endpoints and fields — which is real routing guidance. However, it never resolves the ambiguity it creates by saying dedicated per-endpoint tools also exist; there is no rule for when to pick this generic tool over garmin_get_daily_summaries or garmin_get_activity.

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?