Skip to main content
Glama
Garmin Health Connect

Garmin Health Connect

by NevoNadav

garmin_heart_rate_zones

Read-onlyIdempotent

Retrieve configured heart rate zones, including sport-specific settings when available, to tailor training intensity and analyze workouts.

Instructions

Read configured heart rate zones, including sport-specific settings if available.

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_heart_rate_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is clear. The description adds only that sport-specific settings may be included if available, which signals response variability, but does not cover return format, prerequisites, 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?

A single tight sentence with no wasted words. The purpose is front-loaded and the sport-specific caveat is appended efficiently.

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?

For a no-parameter read tool with an output schema and annotations covering safety, the description gives enough context to call it correctly. It does not mention authentication or Garmin connection prerequisites, but those are likely platform-level concerns handled elsewhere, so the gap is minor.

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?

There are zero parameters, so parameter semantics are not a concern; the baseline for a no-param tool is 4. The schema has 100% description coverage but contains no properties to document, and the description appropriately does not discuss parameters.

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?

States a specific verb and resource: 'Read configured heart rate zones', and adds scope with 'including sport-specific settings if available'. The word 'configured' distinguishes it from a live heart-rate reading sibling like garmin_heart_rate, but the description never names or explicitly contrasts with that sibling.

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?

Usage is implied by 'Read configured heart rate zones' – an agent can infer this is for retrieving zone configuration rather than live heart-rate data. However, there is no explicit when-to-use statement, no exclusion, and no named alternative; guidance remains implicit.

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