Skip to main content
Glama
google-health-mcp

google-health-mcp

health_get_activity

Retrieve daily activity summaries including steps, calories, active minutes, and distance from a local cache, or fetch live data for a date range via the API.

Instructions

Get daily activity summaries (steps, calories, active minutes, distance).

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

Note: live=True fetches one API call per day - avoid large ranges to stay within the 150 requests/hour rate limit.

Args: start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "30d". Default: 30 days 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 this window from the API before reading the cache.

Returns one entry per day with steps, calories, active minutes, distance. active_minutes = very_active + fairly_active (excludes lightly active).

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

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

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses cache-vs-API semantics, the prerequisite sync step, the cost model (one API call per day when live), and a concrete rate limit of 150 requests/hour. It even defines a derived field (active_minutes = very_active + fairly_active, excluding lightly active), which is behavior an agent could not infer from the schema.

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?

It is front-loaded with purpose, then behavior, then constraints, then an Args block, so an agent can stop reading early and still call it correctly. The only minor waste is the partial restatement of live's effect in both the body and the Args section.

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?

There is no output schema, yet the description explains the return shape ('one entry per day with steps, calories, active minutes, distance') and the definition of a non-obvious field. Combined with date-format guidance, cache/live tradeoffs, and rate limits, nothing an agent needs to invoke this three-parameter read tool is missing.

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 schema alone gives no meaning for any of the three parameters, and the description fully compensates. Each parameter gets accepted formats ("YYYY-MM-DD", "YYYY-MM", "30d"/"Nd"), default-resolution rules, and the precise effect of live ('re-fetch this window from the API before reading the cache').

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?

The first line gives a specific verb and resource ('Get daily activity summaries') and enumerates the exact metrics returned (steps, calories, active minutes, distance), which separates it from most siblings like health_get_sleep or health_get_heart_rate. It stops short of distinguishing itself from the closest sibling, health_get_azm / active-zone-minutes, and never mentions health_trends as the aggregate alternative.

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?

It clearly states the operating mode: cache-first by default, live=True to hit the API, and 'Run health_sync first to populate the cache' as an explicit prerequisite. It also warns to avoid large ranges under live=True. It does not name a sibling alternative, so there is no explicit when-not-to-use-this-tool routing.

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