Skip to main content
Glama

garminGet

Read-only

Fetch any Garmin Connect endpoint not covered by other tools by sending a read-only GET request with a custom relative path and optional query string.

Instructions

Generic read-only GET on the Garmin Connect Personal API, for endpoints not covered by the other tools or when a query parameter name has to be adjusted. 'path' is relative and starts with '/', e.g. /fitnessage-service/fitnessage/v2/2026-10-25 . 'query' is an optional URL query string without '?', e.g. date=2026-10-25&foo=bar .

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": "garminGet"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRelative API path starting with /
queryNoQuery string, e.g. a=1&b=2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and unbounded reach are covered. The description usefully adds that the path is relative and must start with '/', but says nothing about response shape (raw JSON?), error behavior for invalid paths, or authentication/session requirements for a tool that can hit arbitrary endpoints.

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 purpose followed by parameter guidance, and both examples earn their place by showing the exact expected format. Minor slack from quoting the field names in a way that repeats the schema.

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?

For a two-parameter escape-hatch tool with no output schema, the definition covers inputs adequately but leaves return format and failure modes unstated. Since results vary by endpoint, a sentence on what comes back (raw JSON pass-through) and what happens on a bad path would materially help an agent recover from errors.

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 real meaning: it supplies a concrete path example and clarifies that the query string must omit the leading '?', which the schema's "a=1&b=2" example does not state.

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 ("Generic read-only GET on the Garmin Connect Personal API") and immediately scopes it as a fallback for endpoints not covered by the other tools. That framing lets an agent distinguish it from the many typed siblings like getSleep or getBodyBattery without inspecting their schemas.

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 explicit use conditions: endpoints not covered by other tools, or when a query parameter name must be adjusted. The alternative (the dedicated per-endpoint tools) is implied as the default choice, though it is not named or presented as an explicit "prefer X first" rule.

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