Skip to main content
Glama
google-health-mcp

google-health-mcp

health_get_height

Retrieve height readings in millimetres from Google Health, using cached data by default with optional date ranges or live refresh for tracking growth and body measurements.

Instructions

Get height readings, in millimetres as Google reports them.

Height is usually logged once, often years back, so the default window is ten years. Returns data from the local cache by default.

Args: start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "Nd". Default: ten years back from the end date or today, whichever is earlier. end_date: End date as "YYYY-MM-DD", "YYYY-MM" (its last day), or "Nd". Default: today. live: If true, re-fetch height from the API before reading the cache.

Returns one entry per reading with datetime, date, height_mm and provider.

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

Input Schema

NameRequiredDescriptionDefault
liveNo
end_dateNo
start_dateNo

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_heightOutput",
      -  "type": "object"
      -}New value: +null
  2. Addedv1.7.0

TDQS

A4/5.0
Behavior4/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 much of it: cache-first reads, an opt-in network re-fetch, a ten-year default window justified by how rarely height is logged, and the exact returned fields. Gaps remain around authentication requirements, pagination, and what happens when the cache is empty and live is false, which is why this is not a 5.

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?

Purpose and the cache/unit caveat are front-loaded, then the per-argument detail follows in a scannable Args block. The sentence about height being logged "once, often years back" earns its place by justifying the ten-year default; wording is slightly padded but nothing is redundant.

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

Completeness4/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 annotations, the description steps in by naming the return shape (datetime, date, height_mm, provider) and the units, so an agent can consume results without opening anything else. Only the cache-miss and auth edge cases are left unaddressed for a read tool of this complexity.

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 and it does: it documents accepted date formats for both bounds ("YYYY-MM-DD", "YYYY-MM", "Nd"), clarifies that a YYYY-MM end_date means its last day, and explains the asymmetric default rule for start_date. Every parameter gains meaning beyond its bare type declaration.

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 height readings") plus the unit and source ("in millimetres as Google reports them"), which separates it cleanly from the weight, sleep, and activity siblings. It does not explicitly name a sibling it should be preferred over, but the resource is unambiguous.

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?

The description explains the caching model ("Returns data from the local cache by default") and gives an explicit condition for the live flag ("If true, re-fetch height from the API"), which is genuine usage guidance. However, it never routes the agent between this tool and related siblings such as health_trends or health_sync, so tool-selection guidance is implied rather than stated.

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