Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

garmin_api_get

Read-only

Fetch data from any Garmin Connect API endpoint not covered by a dedicated tool. Make read-only GET requests with a path and optional query parameters.

Instructions

Raw GET against the Garmin Connect API for endpoints that have no dedicated tool. Read-only; the path must not contain a query string (use params).

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": {
      "path": "<path>"
    },
    "name": "garmin_api_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAPI path, e.g. /usersummary-service/stats/steps/daily/2026-01-01/2026-01-07
paramsNoQuery string parameters

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one real operational constraint (no query string in path, use `params`), but says nothing about authentication needs, error/404 behavior, or that the response is raw untyped API JSON — the things an agent most needs when escaping to a raw endpoint.

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 sentences, zero waste, with the purpose and the 'no dedicated tool' restriction front-loaded ahead of the mechanical constraint.

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 an output schema present and 100% parameter coverage, the description needn't document return values. Purpose, routing rule and the path/params rule are all covered; only failure-mode behavior for an open-world raw call is left unstated.

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 adds genuinely useful semantics: the split between path and params and the prohibition on embedding a query string in the path. Path formatting is also illustrated by the schema example.

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 ('Raw GET against the Garmin Connect API') and explicitly scopes it to 'endpoints that have no dedicated tool', which distinguishes it from the large set of get_* siblings. An agent can route to it 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?

The phrase 'for endpoints that have no dedicated tool' gives a clear selection rule against the ~50 dedicated getters, and 'Read-only' implies writes belong elsewhere. It never names garmin_call explicitly, so the boundary with that sibling must still be inferred.

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