Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_heart_rate_zones

Read-only

Fetch heart rate zone profiles, including default and per-sport settings, from Garmin Connect to guide training intensity accurately.

Instructions

Heart-rate zone profiles: DEFAULT plus any per-sport ones.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 adds return-content context (DEFAULT plus per-sport profiles), but nothing about auth, whether an empty result is possible when zones are unconfigured, or how profiles are structured. Useful but thin addition over the annotations.

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?

A single short fragment with zero padding, and the most important fact (that multiple profiles are returned) is front-loaded. It is arguably too terse to serve as a full definition, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameters, the description is the only place an agent can learn what comes back, and it only sketches that (DEFAULT plus per-sport profiles) without describing zone boundaries or what a profile contains. Adequate to recognize the tool, but not complete for an output-bearing read.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to carry; the baseline for a 0-param tool is 4. The schema simply enforces an empty object with additionalProperties=false.

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 a specific resource (heart-rate zone profiles) and scopes its contents as DEFAULT plus per-sport profiles, which tells an agent what it will get without opening a schema. It lacks an explicit verb, but combined with the name the intent is unambiguous and distinguishable from sibling get_heart_rates (raw samples).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no reference to the sibling tools that operate on the same resource (set_heart_rate_zones, delete_heart_rate_zones, get_heart_rates). The agent must infer that this is the read counterpart purely from the name.

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