Skip to main content
Glama
google-health-mcp

google-health-mcp

health_get_hrv

Retrieve nightly heart rate variability data (RMSSD, entropy, non-REM heart rate) from a local cache or the live API to assess recovery and parasympathetic activity.

Instructions

Get nightly HRV (heart rate variability) data.

Returns data from the local cache by default. Use live=True to fetch from the API. Run health_sync first to populate the cache.

HRV data is sparse: only nights with on-wrist sleep tracking produce readings.

Args: start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "30d". Default: 30 days back from the end date or today, whichever is earlier. end_date: End date as "YYYY-MM-DD", "YYYY-MM" (its last day), or "Nd". Default: today. live: If true, re-fetch this window from the API before reading the cache.

Returns one entry per night with daily_rmssd and deep_rmssd (ms), entropy, non_rem_hr (non-REM heart rate, bpm) and data_source (the device and platform Google says recorded it). RMSSD = root mean square of successive RR interval differences. Higher values generally indicate better recovery and parasympathetic activity.

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": "health_get_hrv"
  }
}

Input Schema

NameRequiredDescriptionDefault
liveNo
end_dateNo
start_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.12.0
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "health_get_hrvOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load, and it does well: it discloses the caching layer, the live re-fetch side effect, the sync prerequisite, and the data-coverage limitation that only on-wrist sleep nights yield readings. It stops short of noting auth requirements, rate limits, or what an empty window returns, so it isn't fully exhaustive.

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, then cache behavior, then Args and Returns blocks, so an agent can stop reading early if it only needs the purpose. Slightly padded by the RMSSD glossary and its interpretation, though those are defensible given the domain jargon. Overall tight with no redundant restatement of the name.

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?

With three optional parameters, no annotations, and no output schema, the description supplies the missing return contract (one entry per night, daily_rmssd/deep_rmssd in ms, entropy, non_rem_hr in bpm, data_source) plus units and device provenance. It leaves gaps on empty-result behavior and any access constraints, but nothing essential to a correct call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: start_date accepts 'YYYY-MM-DD', 'YYYY-MM', or relative '30d' with a stated default of 30 days back from the earlier of end_date or today; end_date accepts a month (its last day) or 'Nd'; live triggers an API re-fetch before the cache read. These are details the bare schema cannot convey.

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: 'Get nightly HRV (heart rate variability) data', which is unambiguous against siblings like health_get_sleep or health_get_heart_rate. The scope ('nightly') and the cache-vs-live framing further narrow it. Sibling differentiation is implicit through the distinct resource rather than explicit naming, so a 4 rather than a 5.

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 operational guidance: cache is the default path, live=True is the alternative when fresh API data is required, and 'Run health_sync first to populate the cache' names the prerequisite tool outright. It also sets expectations about sparsity so the agent isn't surprised by missing nights, which doubles as a when-not-to-trust-results caveat.

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