Skip to main content
Glama

Google Health Physical-Time Rollup

google_health_rollup
Read-onlyIdempotent

Aggregate Google Health data for a specified data type over physical time intervals. Define a date range and interval to get summary metrics.

Instructions

Aggregate a data type over physical time intervals using Google Health rollUp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_timeYesISO 8601 date-time with timezone, e.g. 2026-05-01T00:00:00Z
data_typeNoGoogle 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_sizeNo
page_tokenNo
start_timeYesISO 8601 date-time with timezone, e.g. 2026-05-01T00:00:00Z
window_sizeNoDuration in protobuf seconds format, e.g. 3600s.3600s
privacy_modeNoOptional per-call privacy override. Defaults to GOOGLE_HEALTH_PRIVACY_MODE or structured. raw returns upstream Google Health JSON.
response_formatNomarkdown
data_source_familyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
endpointYes
privacy_modeYes
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds no behavioral details like timezone handling, data merging behavior, or rate limits. Minimal value beyond annotations.

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

Conciseness3/5

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

Single sentence, but lacks substance. It is concise but too short to be informative; does not earn its place fully.

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

Completeness2/5

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

Given 9 parameters, 2 required, and a complex domain with many sibling tools, the description is insufficient. It does not explain 'physical time intervals', window_size, data source family, or how rollup differs from other aggregations.

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

Parameters2/5

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

Schema coverage is 56% with descriptions for many parameters. The description does not add any parameter-level meaning (e.g., explains data_type or window_size semantics). With moderate coverage, description should compensate but does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'aggregate a data type over physical time intervals', which gives a basic purpose. However, it does not distinguish from sibling tools like google_health_daily_rollup or google_health_weekly_summary, making it ambiguous for an agent to choose correctly.

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?

No guidance on when to use this tool versus alternatives (e.g., daily_rollup, list_data_points). No context on prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/google-health-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server