Skip to main content
Glama

getHeartRateZones

Read-only

Retrieves heart rate zones configured in Garmin Connect for each sport, with zone boundaries, max and resting heart rate, and lactate threshold for training intensity analysis.

Instructions

The heart rate zones set in Garmin Connect: a list with one entry per sport that has its own zones (sport DEFAULT for the others), each with trainingMethod (how Garmin sets the zones), zone1Floor to zone5Floor (the lowest bpm of each zone; a zone ends where the next one starts, zone 5 at maxHeartRateUsed), maxHeartRateUsed, restingHeartRateUsed and lactateThresholdHeartRateUsed. It takes no parameters. It gives the limits only: the time in each zone of an activity is hrZonesSec in listActivities.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description nonetheless adds substantial behavior beyond them: no parameters, per-sport zone sets, the rule that a zone ends where the next begins, zone 5 capped at maxHeartRateUsed, and which reference rates are reported. It omits auth/rate-limit context, but for a read-only lookup that is minor.

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 resource and then the return structure; each clause carries information an agent needs to interpret the result. It is dense and written as one long block rather than being broken into shorter statements, but there is no filler.

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?

There is no output schema, so the description carries the return-shape burden and does so thoroughly: field names, zone-boundary semantics, and the reference heart rates. What remains thin is any statement of error cases or freshness, which for a simple read-only lookup is not critical.

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?

With zero parameters the baseline is 4, and the description reinforces it by stating 'It takes no parameters', removing any doubt raised by an empty schema object. No further parameter meaning is needed.

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?

The description names the specific resource (the heart rate zones set in Garmin Connect) and defines its exact shape: one entry per sport with its own zones, DEFAULT for the rest. It is clearly distinguished from data in listActivities, so an agent can tell what this returns without consulting anything else.

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?

It explicitly routes the agent elsewhere for a related need: per-activity time-in-zone lives in hrZonesSec in listActivities, not here. That is a clear alternative plus a scoping statement ('It gives the limits only'), though it does not spell out when not to call it or any prerequisites.

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