Google Health MCP

Overview Schema Source Related Servers Score Discussions Admin

Reconcile Google Health Data Points

google_health_reconcile_data_points

Read-onlyIdempotent

Reconcile health data points for one data type across multiple sources. Retrieve a unified stream from all sources, Google wearables, or Google sources using optional filters.

Instructions

Read a reconciled stream for one data type across sources. Supports all-sources, google-wearables and google-sources data source families.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filter`	No	Optional Google AIP-160 filter expression. Use snake_case field names in filters.
`data_type`	No	Google Health data type in kebab case. Supported slugs (call google_health_list_data_types for units and which verbs each supports): active-energy-burned, active-minutes, active-zone-minutes, activity-level, altitude, blood-glucose, body-fat, calories-in-heart-rate-zone, core-body-temperature, daily-heart-rate-variability, daily-heart-rate-zones, daily-oxygen-saturation, daily-respiratory-rate, daily-resting-heart-rate, daily-sleep-temperature-derivations, daily-vo2-max, distance, electrocardiogram, exercise, floors, food, food-measurement-unit, heart-rate, heart-rate-variability, height, hydration-log, irregular-rhythm-notification, nutrition-log, oxygen-saturation, respiratory-rate-sleep-summary, run-vo2-max, sedentary-period, sleep, steps, swim-lengths-data, time-in-heart-rate-zone, total-calories, vo2-max, weight. Other valid v4 kebab-case slugs are also accepted.	steps
`page_size`	No
`page_token`	No
`privacy_mode`	No	Optional per-call privacy override. Defaults to GOOGLE_HEALTH_PRIVACY_MODE or structured. raw returns upstream Google Health JSON.
`response_format`	No		markdown
`data_source_family`	No
`explicit_user_intent`	No	Required true when privacy_mode=raw (agent escalation of redaction).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`endpoint`	Yes
`privacy_mode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.7Aug 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Addedv0.7.3Aug 4, 2026
Removedv0.5.3Jul 17, 2026

Changed1 schema field changedv0.5.1Jun 29, 2026

changedInput schema / properties / data_type / description

Previous value: -"Google Health data type in kebab case, e.g. steps, sleep, heart-rate, daily-resting-heart-rate."New value: +"Google Health data type in kebab case. Supported slugs (call google_health_list_data_types for units and which verbs each supports): active-energy-burned, active-minutes, active-zone-minutes, activity-level, altitude, blood-glucose, body-fat, calories-in-heart-rate-zone, core-body-temperature, daily-heart-rate-variability, daily-heart-rate-zones, daily-oxygen-saturation, daily-respiratory-rate, daily-resting-heart-rate, daily-sleep-temperature-derivations, daily-vo2-max, distance, electrocardiogram, exercise, floors, food, food-measurement-unit, heart-rate, heart-rate-variability, height, hydration-log, irregular-rhythm-notification, nutrition-log, oxygen-saturation, respiratory-rate-sleep-summary, run-vo2-max, sedentary-period, sleep, steps, swim-lengths-data, time-in-heart-rate-zone, total-calories, vo2-max, weight. Other valid v4 kebab-case slugs are also accepted."

First observedv0.1.3May 7, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already mark this as read-only, open-world, idempotent, and non-destructive; the description's 'Read' is consistent with those attributes. It adds the notion of a reconciled stream across sources, but does not disclose behavior like pagination, privacy-mode effects, or how reconciliation differs from raw listing. With annotations covering the safety profile, this is acceptable but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is exceptionally concise: two sentences, front-loaded with the core verb and object, followed by the supported source families. There is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The core purpose is clear, and the presence of an output schema reduces the need to explain return values. However, for a tool with 8 parameters, the description does not clarify selection versus list_data_points/rollup, and several parameters remain semantically under-specified. It is adequate but not fully complete for an agent encountering this tool in a large sibling set.

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

Parameters3/5

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

Schema description coverage is exactly 50%, so the description is expected to compensate for undocumented parameters. It partially does by listing the three data source family values in prose, but it adds nothing about page_size, page_token, response_format, or default privacy behavior. The description provides marginal value over the schema but does not fill the coverage gap completely.

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?

The description clearly states a specific action ('Read') and a specific resource ('a reconciled stream for one data type across sources'), which is not a tautology of the title. It also lists the supported data source families, adding concrete scope. However, it does not explicitly differentiate itself from siblings like google_health_list_data_points or google_health_rollup.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention google_health_list_data_points, google_health_rollup, or any exclusion criteria, leaving the agent to infer selection without support.

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