google-health-mcp

Overview Schema Source Related Servers Discussions Admin

health_get_exercises

Retrieve tracked exercise sessions by date range or activity type, including duration, calories, heart rate, distance, and optional event details, from cache or live API.

Instructions

Get exercise log entries (individual tracked activities).

Returns exercise sessions from the local cache by default. Use live=True to fetch from the API. Run health_sync first to populate the cache.

Args: start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "30d". Default: last 30 days. end_date: End date as "YYYY-MM-DD". Default: today. exercise_type: Filter by activity name (case-insensitive substring match), e.g. "cycling", "walk", "run". Default: all types. A value matching no workout name the cache holds is refused, naming those, rather than answered as a period with no workouts. live: If true, re-fetch this window from the API before reading the cache. include_detail: If true, include every exercise event (start, pause, stop), split and split summary. Without it each entry carries only how many there are (detail_counts), null where none is stored: an imported workout, one Google sent none for, one synced before these were fetched, or a stored value that cannot be read.

Returns exercise entries with name, duration, calories, avg heart rate, distance, and source (for a synced workout the recording device's name, and data_source.recordingMethod says whether it was logged by hand; for an imported one whatever the import carried), and for a synced workout also start and end times with their UTC offsets, active_seconds, notes, Google's metrics_summary whole (pace, speed, elevation, heart-rate zone durations, mobility), exercise_metadata (hasGps, pool length) and data_source. Note: HR data from cycling may be unreliable (optical sensor vs handlebar grip).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`live`	No
`end_date`	No
`start_date`	No
`exercise_type`	No
`include_detail`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.7.0Sep 30, 2026

addedInput schema / properties / include_detail

Added value: +{
+  "default": false,
+  "title": "Include Detail",
+  "type": "boolean"
+}

First observedv1.0.0Aug 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it explains cache vs live API behavior, the health_sync dependency, what include_detail changes, how detail_counts can be null, and even warns that cycling HR data may be unreliable.

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?

Purpose, Args, and usage guidance are front-loaded and useful, but the long Returns paragraph repeats what an output schema already conveys. Since the context notes an output schema exists, much of that return-field enumeration is redundant and makes the description longer than necessary.

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?

Given five parameters, no schema descriptions, no annotations, and a cache/live data model, the description is complete enough to call correctly. It covers prerequisites, parameter meanings, edge cases, and output semantics.

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 must compensate. It documents all five parameters, including date input formats, defaults, case-insensitive substring matching for exercise_type, and the unusual refusal behavior when no cache workout name matches.

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 first sentence gives a specific verb and resource: 'Get exercise log entries (individual tracked activities).' It distinguishes this from sibling activity tools by specifying individual tracked exercise sessions rather than general activity or sleep data.

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?

The description clearly states the default cache-based behavior, when to use live=True, and the prerequisite to run health_sync first. It does not explicitly name a sibling alternative or state when not to use this tool, so it falls slightly short of a 5.

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