Skip to main content
Glama
google-health-mcp

google-health-mcp

health_get_lifetime_stats

Retrieve all-time steps, floors, distance and calorie totals plus personal best day records, with a coverage block showing the synced date range and days counted.

Instructions

Get all-time activity totals and personal best records.

Totals for steps, floors, distance and calories over every day held in the cache, plus the best single day for steps, floors and distance with the date each record was set.

The answer is bounded by what has been synced, so it is returned with a coverage block giving the first and last dates and the number of days counted - read it before quoting a total as all-time. There is no tracker-versus-total split and no "active score"; neither has a source.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose important behavior: results are bounded by what has been synced, a `coverage` block with first/last date and day count accompanies the answer, and certain metrics contain no source. It omits auth or performance characteristics, but the data-integrity caveats are exactly what an agent needs before quoting numbers.

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?

Three short paragraphs, front-loaded with what is returned, then the caveat about coverage, then the explicit non-existence of tracker/total split and 'active score'. Every sentence contributes, though the final sentence sits slightly apart from the rest structurally.

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?

With no output schema and no parameters, the description fully compensates by naming the returned sections (totals, personal bests with dates, coverage block). An agent has everything needed to call it and interpret the result without further documentation.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies.

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?

States a specific verb and resource ('Get all-time activity totals and personal best records') and enumerates the exact metrics returned (steps, floors, distance, calories) plus best-day records. The 'all-time' scope implicitly separates it from health_get_activity and health_trends, but it never names those siblings, so differentiation is left to inference.

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

Usage Guidelines3/5

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

There is implied usage for lifetime summaries, and one real piece of operational guidance: read the `coverage` block before quoting a total as all-time. However, it gives no explicit when-to-use-this-vs-health_get_activity or health_trends guidance and no exclusions.

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