Skip to main content
Glama

get_hrv

Read-onlyIdempotent

Retrieve nightly heart rate variability (HRV) over a date range, with last-night and weekly averages, 5-minute highs, status, and personal baseline for Garmin sleep insights.

Instructions

T3. Heart rate variability (HRV) per night over a date range: last-night average, weekly average, 5-minute high, status and personal baseline, in milliseconds. Each night is labelled woke_up_on, the morning it ended. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "get_hrv"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesLast date, YYYY-MM-DD (inclusive); at most 90 days after start.
startYesFirst date, YYYY-MM-DD (inclusive).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds materially useful behavioral context beyond them: the per-night record is keyed by the morning it ended (woke_up_on), missing fields read as 'not recorded' and must never be treated as zero, and results are informational rather than medical. These caveats directly change how an agent interprets and reports the data.

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 metric list and units are front-loaded, followed by the labeling rule and the null-handling caveat, so every sentence earns its place. Minor deduction for the unexplained 'T3.' prefix, which is noise an agent cannot act on.

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?

With an output schema present, the description needn't enumerate return values, and it covers the remaining interpretive essentials: units, night labeling, the 90-day window (via schema), and how to treat unrecorded fields. Nothing an agent needs in order to call and interpret this 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 description coverage is 100% – both start and end are documented with YYYY-MM-DD format and the 90-day constraint on end. The description only reinforces the date-range framing and adds no syntax or edge-case detail beyond the schema, so the baseline 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?

The description names a specific verb+resource (heart rate variability per night) and enumerates the returned measures (last-night average, weekly average, 5-minute high, status, personal baseline) with units in milliseconds. This is clearly distinguishable from siblings like get_heart_rate or get_sleep without opening either schema.

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?

The date-range scoping is implied by 'over a date range', and the schema states the 90-day cap, but the description never says when to pick this tool over get_heart_rate, get_sleep, or trend, nor any exclusions or prerequisites. Usage is inferable from the resource name only.

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