Skip to main content
Glama
google-health-mcp

google-health-mcp

health_get_spo2

Retrieve nightly blood oxygen saturation (SpO2) readings from a local health cache to analyze sleep oxygen trends; sync health data first to populate nights with on-wrist tracking.

Instructions

Get nightly SpO2 (blood oxygen saturation) data.

Returns data from the local cache by default. Run health_sync first to populate it.

SpO2 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: avg SpO2 percentage and up to two pairs of bounds. avg_ci_low/avg_ci_high come from this API, which Google describes as the lower and upper bound of the confidence interval of oxygen saturation samples during sleep. min/max hold whatever an import carried; on the history checked, they matched avg_ci_low/avg_ci_high on every night carrying both. std_dev is Google's standard deviation of the daily SpO2 averages over the past 7-30 days, not of this night's samples, and data_source the device and platform Google says recorded it. Normal range: 95-100%. Below 90% may indicate sleep apnea.

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

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_spo2Output",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

With zero annotations the description carries the full burden and does so: cache-by-default read behavior, the sync dependency, the sparsity caveat (only nights with on-wrist sleep tracking), and a warning that min/max may merely mirror the confidence bounds from imports. It also documents the non-obvious std_dev window (7-30 days, not the night's samples) and gives clinical context for interpreting values.

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-loads purpose, then the cache note, then parameter docs, then return values and interpretation. Nearly every sentence is load-bearing, though the comparative discussion of min/max versus avg_ci_low/avg_ci_high is a touch wordy and could be tightened.

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, and the description compensates by describing the per-night entry shape, what each bound means, the provenance of std_dev and data_source, and a reference range for interpreting results. Nothing needed to call or interpret the tool 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 coverage is 0% and the schema is bare strings with no descriptions, yet the description supplies accepted formats for start_date ('YYYY-MM-DD', 'YYYY-MM', '30d') and end_date (including that YYYY-MM resolves to its last day and Nd is relative), plus the defaults and the exact effect of live.

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?

Opens with a specific verb and resource, 'Get nightly SpO2 (blood oxygen saturation) data', and spells out the acronym so it is unmistakeably distinct from siblings like health_get_heart_rate and health_get_hrv.

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

Usage Guidelines4/5

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

Gives an explicit prerequisite ('Run health_sync first to populate it') and explains the cache-vs-API decision via the live flag. It stops short of stating when a caller should prefer a fresh live fetch over the populated cache, so no explicit exclusion rules are present.

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