Skip to main content
Glama
google-health-mcp

google-health-mcp

health_get_azm

Retrieve daily Active Zone Minutes with fat burn, cardio, and peak zone breakdowns. Reads from a local cache and auto-syncs when stale, so you can track cardio intensity trends.

Instructions

Get daily Active Zone Minutes (AZM), the headline cardio metric.

AZM counts minutes spent in heart rate zones at or above Fat Burn intensity. total_minutes is the plain sum of the three zone columns as reported, not a weighted one. Returns from local cache by default, auto-syncing if stale.

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 day with total_minutes plus per-zone breakdown (fat_burn_minutes, cardio_minutes, peak_minutes). Distinct from active_minutes in health_get_activity, which counts wall-clock minutes regardless of intensity - and which has no source in this API, so it is present only for days that arrived by import.

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

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

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description must carry the full load. It clearly discloses that results come from a local cache by default with automatic sync when stale, that `live` forces a fresh API fetch, and that `total_minutes` is a plain sum rather than a weighted value. That is meaningful behavioral context beyond a bare 'get'.

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 front-loaded with the purpose and definition, then proceeds through args, returns, and the sibling distinction in a predictable order. Minor redundancy in the date-default explanation keeps it from being maximally tight.

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 no output schema and no annotations, the description supplies exactly what is missing: the return shape (one entry per day with total_minutes plus per-zone breakdown), the caching model, and the distinction from the nearest sibling. An agent has enough to call this correctly and interpret the result.

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 has to do all the work, and it does: the accepted date formats ("YYYY-MM-DD", "YYYY-MM", "30d", "Nd"), the meaning of a month-only end date (its last day), and the default window logic are all spelled out. The `live` parameter is likewise explained as a cache-bypass re-fetch rather than merely named.

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 opens with a specific verb and resource: 'Get daily Active Zone Minutes (AZM), the headline cardio metric.' It goes further to define what AZM actually counts (minutes in heart rate zones at or above Fat Burn), and it explicitly separates the tool from the confusingly similar active_minutes metric in health_get_activity.

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?

It provides clear contextual guidance: the tool is for zone-based intensity minutes rather than wall-clock active minutes, and it explains when the cache is used and when auto-sync kicks in. It stops short of naming alternative tools such as health_trends or health_get_heart_rate for related questions, but the sibling differentiation it does give is specific and useful.

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