Skip to main content
Glama

get_heart_rate_zones

Read-only

Retrieves saved Garmin heart-rate training-zone profiles, including default and sport-specific settings, or filters results to one sport by key.

Instructions

Get the user's saved heart-rate training-zone configuration.

    Garmin stores a generic DEFAULT profile plus optional sport-specific
    overrides such as RUNNING and CYCLING. With no sport, this returns every
    saved profile; pass a sport key to return just that profile.

    Args:
        sport: Optional Garmin sport key (for example default, running, or
               cycling). "generic" is accepted as an alias for DEFAULT.
    

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

Input Schema

NameRequiredDescriptionDefault
sportNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the stored model of a generic DEFAULT profile plus optional sport-specific overrides, and the consequence that omitting sport widens the result set. It does not mention caching, permissions, or response shape, which keeps it below 5.

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?

The substantive part is front-loaded in the first paragraph and every sentence carries information. The indented docstring-style Args block is somewhat heavier formatting than needed for a single optional parameter, and the sport explanation restates the prior paragraph, but nothing is genuinely wasteful.

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 one optional parameter, no output schema and read-only annotations, the definition covers what an agent needs to call it correctly, including default-vs-filtered return scope and accepted key values. The only gap is the structure of the returned profiles, but that is reasonably outside scope for a read-only getter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the schema only names a nullable "Sport" string with a null default — so the description must carry the meaning, and it does: it identifies the parameter as an optional Garmin sport key, gives concrete example values (default, running, cycling), and documents the "generic" alias for DEFAULT. None of that is recoverable from the schema.

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 opens with a specific verb and resource: "Get the user's saved heart-rate training-zone configuration." It then clarifies that the resource is a saved configuration profile rather than a time-series, which is exactly the distinction needed against siblings like get_heart_rates and get_heart_rates_summary.

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 gives clear selection logic for the one decision an agent faces: omit sport to return every saved profile, or pass a sport key to scope to one. It does not name alternatives such as set_heart_rate_zones or get_heart_rates, nor state when not to use it, so it falls short of a 5.

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