Skip to main content
Glama

Get heart rate zones

garmin_get_heart_rate_zones
Read-only

Retrieve heart rate zone floors per sport, plus the training method and resting, max, and lactate threshold heart rates used to build them. Generate defaults if none are configured.

Instructions

Heart rate zone floors per sport, with the training method and the resting, max, and lactate threshold heart rates the zones were built on.

generate_defaults: return Garmin's default zones when none are configured.

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
generate_defaultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/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 the safety profile is covered. The description usefully discloses what the response contains (zone floors, method, reference HRs), but says nothing about auth requirements, per-sport coverage limits, or behavior when generate_defaults is explicitly false.

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?

Two short sentences, front-loaded with what the tool returns before the parameter behavior. The mid-sentence line break is slightly awkward but nothing is wasted.

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 and a single optional param, the description covers the essential return content and the main parameter behavior. Missing only edge-case behavior for generate_defaults=false, which an agent could plausibly need.

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 0%, so the description carries the param burden and does so reasonably: it explains that generate_defaults returns Garmin's default zones when none are configured. It does not explain the false case or that the default is true, leaving a small gap.

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?

The description names the resource precisely ('heart rate zone floors per sport') and lists the accompanying data (training method, resting/max/lactate threshold HRs), which clearly separates it from garmin_get_heart_rate readings. It stops short of explicitly differentiating itself from siblings like garmin_get_profile or garmin_get_fitness_age, which may also surface related metrics.

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 generate_defaults sentence implies when that flag is useful ('when none are configured'), which is a mild usage cue, but there is no guidance on when to call this tool versus garmin_get_heart_rate or other wellness tools. Usage must be inferred.

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