Skip to main content
Glama
garmin-connect-mcp

garmin-connect-mcp

by Samiu1

Get Heart Rate Zones

garmin_get_heart_rate_zones
Read-onlyIdempotent

Retrieve your configured heart-rate training zones and their BPM boundaries. Use them to interpret averageHR and maxHR values from Garmin activities.

Instructions

Get the user's configured heart-rate training zones, including the boundary beats per minute for each zone. Useful for interpreting the averageHR and maxHR on activities.

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
response_formatNo'markdown' for readable text, 'json' for the exact Garmin field names and valuesmarkdown
generate_defaultsNoReturn Garmin's default zones when the user has configured none
include_empty_fieldsNoKeep fields Garmin returned as null or empty. Off by default, since unsupported sensors on the user's device produce large runs of nulls. Turn on only to inspect raw shape.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds that the zones are user-configured and what the boundaries mean, but says nothing about what happens when no zones exist (delegated to the generate_defaults parameter in the schema), auth requirements, or rate limits.

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?

Two short sentences, zero waste: purpose and returned content first, then the practical use case. It is front-loaded and appropriately sized for a simple read tool.

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 carries the burden of describing returns and does name the key content (zone boundaries in bpm). The empty/no-zones case is handled only indirectly via the schema parameter, and the output shape is otherwise unspecified, leaving a small gap.

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 description coverage is 100%, with all three optional parameters (response_format, generate_defaults, include_empty_fields) documented in detail including defaults and rationale. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 configured heart-rate training zones') and names the payload ('boundary beats per minute for each zone'). The resource is clearly distinct from the activity, daily-health, and raw-data siblings, so an agent can select it without opening the schema.

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?

The second sentence gives a concrete use case: interpreting averageHR and maxHR on activities, which implicitly points at garmin_get_activity as the companion tool. It stops short of explicit when-not conditions or naming alternatives, so it is clear context rather than full routing guidance.

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