Skip to main content
Glama

getHrvRange

Read-only

Retrieves overnight HRV data for a date range, returning nightly averages, 7-night trends, status, and baseline range to track recovery trends over up to 28 days.

Instructions

Overnight HRV for a date range, yyyy-MM-dd: hrvSummaries, one row per night with HRV data (a night without data has no row), with calendarDate, lastNightAvg (ms, the average of the night), lastNight5MinHigh, weeklyAvg (the 7-night average), status (BALANCED, UNBALANCED or LOW) and baseline (balancedLow to balancedUpper: the normal range). Ask at most 28 days in one call: Garmin may refuse a longer range. Use it for the HRV trend; for the sleep of a night use getSleep, and for resting HR use getDailyHeartRate or getDailySummary.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fromDate": "<fromDate>",
      "toDate": "<toDate>"
    },
    "name": "getHrvRange"
  }
}

Input Schema

NameRequiredDescriptionDefault
toDateYesTo date yyyy-MM-dd
fromDateYesFrom date yyyy-MM-dd

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real behavior beyond them: the provider may refuse ranges over 28 days, and nights without data produce no row rather than a null entry. It does not cover error handling beyond the range refusal or any rate limiting, which keeps it from a 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?

Front-loaded with purpose and return shape, then constraints, then alternatives -- a sensible order with no filler. It is dense to the point of a single run-on block, which slightly hurts scanability but every clause carries information.

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

Completeness5/5

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

There is no output schema, yet the description enumerates every returned field (calendarDate, lastNightAvg, lastNight5MinHigh, weeklyAvg, status values, baseline bounds), so an agent knows exactly what comes back. Combined with the range limit and sibling routing, nothing needed to call it correctly is missing.

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 coverage is 100% and both parameters already document the yyyy-MM-dd format, so the schema does the heavy lifting. The description adds only the 28-day range constraint on those parameters, which is useful but modest; baseline 3 fits.

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 ('Overnight HRV for a date range') plus the exact return shape (hrvSummaries, one row per night). It is unmistakable against getSleep and getDailyHeartRate, which are named for the adjacent use cases.

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

Usage Guidelines5/5

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

Gives explicit routing: use this for HRV trend, getSleep for a night's sleep, getDailyHeartRate or getDailySummary for resting HR. It also names a hard operational limit ('at most 28 days in one call: Garmin may refuse a longer range'), which is a when-to-use constraint an agent cannot infer.

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