Skip to main content
Glama
google-health-mcp

google-health-mcp

health_get_weight

Retrieve daily weight, BMI, and body fat percentage logs from a local cache or the live API for a chosen date range, enabling weight trend tracking.

Instructions

Get weight log entries (weight, BMI, body fat percentage).

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

Weight data is sparse: only days with weigh-in entries are present.

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 weight_kg, bmi, fat_pct. Every individual weigh-in is in health_get_weight_readings.

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

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

TDQS

A4.7/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 load and does so well: it discloses the cache-by-default read path, that live=True triggers an API re-fetch of the window (a side effect), and that data is sparse with only weigh-in days present. It stops short of covering API failure behavior, rate limits, or whether the re-fetch overwrites the cache.

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 is front-loaded in the first line, behavior and the sibling pointer follow, and the Args block is scoped to the parameters. A few lines restate the same caching idea twice ("local cache by default" and the live arg note), but overall wording is tight.

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, and the description compensates by describing the return shape per day (weight_kg, bmi, fat_pct) and the sparsity caveat. For a three-parameter, no-annotation read tool, nothing an agent needs to call it correctly 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 description must compensate, and it does: it documents accepted formats for start_date ("YYYY-MM-DD", "YYYY-MM", or "30d") and end_date (including that a month resolves to its last day), plus default-resolution rules. It also explains what live=True does operationally rather than just restating the boolean.

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 description opens with a specific verb and resource ("Get weight log entries") and enumerates the fields returned (weight, BMI, body fat percentage). It also distinguishes itself from its closest sibling by stating that "Every individual weigh-in is in health_get_weight_readings."

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

Usage Guidelines5/5

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

It explicitly routes the agent between live and cached modes ("Returns data from the local cache by default. Use live=True to fetch from the API") and states a prerequisite ("Run health_sync first to populate the cache"). It also names the alternative sibling tool for per-weigh-in granularity.

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