Skip to main content
Glama
google-health-mcp

google-health-mcp

health_trends

Analyze cached health data trends by computing averages and totals across weekly, monthly, or quarterly periods, comparing date ranges, and auto-syncing stale data when needed.

Instructions

Analyse trends in cached health data.

Computes averages and totals over time from the local cache, auto-syncing if stale.

Args: data_type: What to analyse. Options: "heart_rate", "activity", "exercises", "sleep", "weight", "spo2", "hrv", "azm", "breathing_rate", "skin_temperature", "core_temperature", "cardio_fitness", "food_log". Default: "activity". period: Aggregation period. Options: "weekly", "monthly", "quarterly". Default: "monthly". start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "365d". Default: 365 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. compare: Compare two periods. Format: "last_30d vs previous_30d", "2026-03 vs 2026-02", "2026-Q1 vs 2025-Q4". When set, period/start_date/end_date are ignored.

Returns aggregated averages per period. For activity: steps, distance, active minutes. For exercises: sessions, duration, calories. For sleep: duration, efficiency, stage breakdown. For heart_rate: resting HR min/avg/max. For weight: weight, fat%, BMI. For hrv: daily and deep RMSSD.

For cardio_fitness, avg_vo2_max_low/high average a reported band while avg_vo2_max averages a single value: two definitions, each with the count of readings behind it, never one series.

For spo2, min_spo2/max_spo2 are the lowest and highest bound among imported nights (counted by nights_observed_extremes), and avg_nightly_ci_low/avg_nightly_ci_high the mean of the nightly bounds this API reports (counted by nights_confidence_interval).

These fields and their counts appear in the period form only. compare= reports spo2 as avg_spo2 alone, and carries both cardio_fitness definitions.

For core_temperature, a reading whose value was changed in the app is counted as well as its earlier value, in both forms: check a high max_temp_celsius or readings_ge_38c with health_get_core_temperature.

Not for raw data - use health_get_* tools instead.

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

Input Schema

NameRequiredDescriptionDefault
periodNomonthly
compareNo
end_dateNo
data_typeNoactivity
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_trendsOutput",
      -  "type": "object"
      -}New value: +null
  2. Changed2 schema fields changedv1.7.0
    • addedInput schema / properties / data_type / enum
      Added value: +[
      +  "heart_rate",
      +  "activity",
      +  "exercises",
      +  "sleep",
      +  "weight",
      +  "spo2",
      +  "hrv",
      +  "azm",
      +  "breathing_rate",
      +  "skin_temperature",
      +  "core_temperature",
      +  "cardio_fitness",
      +  "food_log"
      +]
    • addedInput schema / properties / period / enum
      Added value: +[
      +  "weekly",
      +  "monthly",
      +  "quarterly"
      +]
  3. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses cached-data use, auto-syncing when stale, compare-mode overrides, count-bearing return fields, and special handling such as core-temperature readings counted with both old and changed values. It also explains that certain fields appear only in period form and not in compare form.

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 description is long but well structured, with purpose first, then Args, Returns, special cases, and the raw-data exclusion. The density is largely justified by 13 data types and five parameters, though some special-case prose could be tightened without losing meaning.

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?

No output schema is present, so the description must explain returns; it does so for most major data types and calls out important edge cases for cardio_fitness, spo2, and core_temperature. It does not spell out return semantics for every data_type such as azm, breathing_rate, skin_temperature, or food_log, leaving a small completeness gap.

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: every parameter is documented with allowed values, defaults, accepted date formats, and interaction rules. It goes beyond the schema by explaining that compare overrides period/start_date/end_date and by giving concrete compare syntax examples.

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: 'Analyse trends in cached health data' and 'Computes averages and totals over time'. It explicitly distinguishes itself from the raw-data sibling family with 'Not for raw data - use health_get_* tools instead.'

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 an explicit exclusion and alternative: use health_trends for aggregated trends, not raw data, which should go through health_get_* tools. It also clarifies the compare parameter's precedence over period/start_date/end_date, removing a key usage ambiguity.

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