Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_hrv

Read-only

Retrieve one night's heart rate variability, including average, 5-minute high, weekly average, personal baseline band, and HRV status to assess recovery and stress.

Instructions

Heart rate variability for one night: last-night average, 5-minute high, weekly average, personal baseline band and HRV status (e.g. BALANCED, UNBALANCED, LOW).

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

Input Schema

NameRequiredDescriptionDefault
dateNoDate as YYYY-MM-DD in the user's time zone. Leave empty for today.
include_readingsNoAlso return every 5-minute HRV reading of the night.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 the status vocabulary (BALANCED, UNBALANCED, LOW) and the notion of a personal baseline band, which is useful behavioral context, but it does not discuss data availability, date range limits, or what happens when no reading exists for a night.

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, front-loaded sentence that states the resource and its scope before listing returned fields. Nothing is wasted, though the field enumeration partially duplicates the output schema and could be trimmed.

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 simple two-parameter read with an output schema and full schema coverage, the description tells the agent what data it will get and over what time window. The main residual gap is routing guidance relative to get_hrv_summaries and other wellness siblings.

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 both date and include_readings fully documented in the schema itself, so baseline is 3. The description adds only a marginal hint that the call is scoped to one night's data and says nothing further about the date format or what include_readings expands to.

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 variability) and constrains it to a single night, then enumerates the exact metrics returned (average, 5-minute high, weekly average, baseline band, status). It is clearly distinguishable from a sleep or heart-rate tool, though it never explicitly separates itself from the sibling get_hrv_summaries by naming it.

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 only implied by the phrase 'for one night', which suggests this is the single-night detail view versus a summarized one. There is no explicit when-to-use or when-not-to-use guidance, and no mention of the obvious alternative get_hrv_summaries.

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