Skip to main content
Glama
google-health-mcp

google-health-mcp

health_get_profile

Retrieve the account's profile, settings, and irregular-rhythm enrolment from the local cache, or re-fetch them from the Google Health API when live is true.

Instructions

Get the account's profile, settings and irregular-rhythm enrolment.

Each is the record Google returns, kept whole: the profile carries age, membership start and stride lengths, the settings carry units, time zone and locale, and the enrolment says whether irregular-rhythm notifications are on. Returns data from the local cache by default.

Args: live: If true, re-fetch the records from the API before reading the cache.

Returns profile, settings and irn_profile, and when each was fetched (UTC). A record is null when it has never been fetched, which includes one whose permission the grant lacks.

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

Input Schema

NameRequiredDescriptionDefault
liveNo

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

TDQS

A3.8/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 burden and does a solid job: it discloses the cache-first default, the refetch semantics of live, the exact return keys, and the meaningful null case (never fetched, or permission missing from the grant). It does not state that the operation is read-only in effect, nor any latency or rate-limit cost of a live refetch of three records.

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?

The core purpose and the cache default are front-loaded, and the field-by-field characterisation of each record is genuinely useful. There is mild redundancy between the body paragraph and the explicit Returns section, both covering what comes back, but nothing is wasted enough to obscure the call.

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?

For a one-parameter read tool with no annotations and no output schema, the description supplies what an agent needs: the return shape, timestamp inclusion, null semantics, and cache behavior. The remaining gap is behavioural on failure — whether a missing permission surfaces as null only or as an error — which slightly limits error-path confidence.

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?

Schema coverage is 0% and the single parameter is undocumented in the schema, so the description must compensate — and it does, explaining that live triggers an API re-fetch before the cache read, on top of the stated cached default. It could still say what a live fetch costs or whether it refreshes all three records, which keeps it short of a 5.

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 a concrete resource set: profile, settings, and irregular-rhythm enrolment. It is clear what comes back, but it never distinguishes itself from siblings such as health_get_irregular_rhythm or health_get_devices, so an agent must infer that this is the account-level summary rather than a data-series tool.

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 gives real guidance for the cache-vs-live decision ('Returns data from the local cache by default' and 'If true, re-fetch the records from the API before reading the cache'), which tells an agent when to pass live: true. It offers no guidance on when to prefer this tool over health_get_irregular_rhythm, health_sync, or the per-metric siblings, and no explicit exclusions.

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