No user-submitted related servers found.
Scored across 24 tools
There are several deliberate near-pairs (health_get_sleep vs health_get_sleep_sessions, health_get_weight vs health_get_weight_readings, health_get_skin_temperature vs health_get_core_temperature, health_trends vs the raw health_get_* tools), but each description explicitly states how it differs from its sibling and points to the right alternative. An agent can pick correctly without guessing, though it must read the descriptions carefully rather than infer from names alone.
Nearly everything follows the health_<verb>_<noun> snake_case pattern (health_get_heart_rate, health_sync), and related tools form clear families. The only deviation is health_trends, which omits a verb, making its action ('analyse') less predictable than the rest.
24 tools is on the heavy side, but the Google Health surface genuinely spans ~15 distinct metric types plus sync, aggregation, profile and device state, and each tool maps to one resource. The granularity variants (sleep sessions, weigh-ins, routes, lifetime stats) each add real capability rather than duplicating.
The set covers the full read lifecycle: cache sync/backfill, raw per-type reads for every metric the API exposes, aggregates (health_trends), lifetime totals, profile/settings, devices, ECG waveforms and exercise GPS routes. It is read-only, but that reflects the underlying API rather than a gap in the surface.