Skip to main content
Glama
Garmin Connect MCP

Garmin Connect MCP

by pedrokehl

Get heart rate zones

garmin_get_heart_rate_zones
Read-onlyIdempotent

Retrieve heart rate zone settings for each sport, including training method, zone thresholds, and max, resting, and lactate threshold heart rates. Generate default zones when none are configured.

Instructions

Get the user's heart rate zone configuration, one entry per sport (default, running, cycling…): training method (%max HR, %HRR or %LTHR), zone1Floor..zone5Floor (bpm), and the max, resting and lactate threshold heart rates used.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "garmin_get_heart_rate_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault
generateDefaultsNoGenerate default zones when the user has none configured. Garmin default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds useful content context (what configuration fields are returned), but omits the notable side effect implied by generateDefaults, which can create default zones when none exist — relevant behavior for an otherwise 'read-only' tool.

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?

A single front-loaded sentence: purpose first, then a compact enumeration of returned fields. No filler or repetition.

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 usefully enumerates the return shape (training method, zone floors, max/resting/LTHR HRs), which is exactly what an agent needs. It only falls short on the generateDefaults side effect and multi-sport edge cases.

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% with a single, well-described parameter, so the schema carries the load. The description adds no extra parameter meaning, which is acceptable at this coverage level (baseline 3).

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 ('Get the user's heart rate zone configuration') and further specifies the granularity ('one entry per sport'). This clearly separates it from siblings like garmin_get_heart_rate (measurements) or garmin_get_user_settings (general settings).

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?

The read-only getter intent is implied by the description, but there is no explicit when-to-use guidance, no named alternatives, and no mention of when zones might be absent or how generateDefaults interacts with usage. Minimum viable.

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