Skip to main content
Glama
google-health-mcp

google-health-mcp

health_get_irregular_rhythm

Retrieve watch-recorded irregular heart rhythm notifications to review possible atrial fibrillation alerts over a chosen date range.

Instructions

Get irregular heart rhythm notifications raised by the watch.

These are background checks the watch runs while the user is still - an alert means it saw a rhythm consistent with atrial fibrillation over one or more windows, not a diagnosis. Most accounts never have one. For a deliberate reading with a trace behind it, use health_get_ecg.

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 notification with start_time, end_time and alert_windows (the periods that triggered it).

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

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

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that these are background still-period checks, that an alert means an AFib-consistent rhythm over one or more windows rather than a diagnosis, and that reads come from a cache unless live is set. Remaining gaps are minor for a read-only tool (no mention of API failure behavior when live=true, no rate-limit or auth context).

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 the purpose and the key caveat before the args, and the Args/Returns sections are easy to scan. Slightly longer than strictly necessary — the default-date explanation is wordier than it needs to be — but no sentence is filler.

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, yet the description names the return shape (start_time, end_time, alert_windows and what those windows mean). Combined with format specs for every parameter and the empty-result caveat, an agent has everything needed to call and interpret this tool correctly.

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%, so the description must compensate and it does: it documents all three parameters, gives accepted formats ("YYYY-MM-DD", "YYYY-MM", "30d", "Nd"), and clarifies end_date's month handling as its last day. It even supplies a real default semantics for start_date (30 days back from end_date or today, whichever is earlier) that the schema's null default does not convey.

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 ("Get irregular heart rhythm notifications raised by the watch") and immediately scopes what those notifications are: background still-period checks, not diagnoses. It explicitly separates itself from the sibling health_get_ecg, so an agent can choose between them without opening either schema.

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 alternative and the condition that selects it: "For a deliberate reading with a trace behind it, use health_get_ecg." It also pre-empts a common misread by warning that most accounts never have a notification, so an empty result is not a failure signal.

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