Skip to main content
Glama
Google Health MCP — Remote

Google Health MCP — Remote

Google Health Daily Summary

google_health_daily_summary
Read-onlyIdempotent

Build a practical daily health summary from Google Health rollups and reconciled streams, with date and timezone options for read-only, non-medical reporting.

Instructions

Build a practical daily summary from Google Health rollups and reconciled streams when available. Read-only, beta, non-medical.

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": "google_health_daily_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNotoday
timezoneNoIANA timezone used to resolve "today" and the day windows, e.g. America/New_York. Defaults to the profile timezone, then UTC.
response_formatNomarkdown

Output Schema

NameRequiredDescriptionDefault
kindYes
generated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context — beta status, non-medical scope, and that data may come from rollups and reconciled streams only "when available" — but says nothing about coverage, latency, or what the summary comprises.

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?

Two short sentences, front-loaded with the operation and immediately followed by scope caveats; nothing is buried. Minor waste in soft qualifiers like "practical" and "when available" that could have been replaced with concrete facts.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the optional-parameter set is small. Still, with 33% schema coverage and no sibling differentiation, an agent lacks the guidance needed to choose this tool confidently over the adjacent rollup and summary tools.

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

Parameters2/5

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

Schema description coverage is only 33%: timezone is documented in the schema, but date's accepted "today" literal and response_format's markdown/json choice carry no explanation anywhere. The description adds no parameter meaning, leaving it short of compensating for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Build a practical daily summary from Google Health rollups and reconciled streams" gives a verb and a resource, and hints that it composes over rollups/existing reconciled data. But "practical" and "summary" are fuzzy, and the definition never distinguishes itself from the very similar sibling google_health_daily_rollup or from google_health_weekly_summary, so an agent cannot tell which one to pick from the text alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated preconditions (e.g. connection/authentication, data availability), and no named alternatives among the 25 siblings. "When available" gestures at partial data but does not tell an agent when to prefer this tool over google_health_daily_rollup or google_health_wellness_context.

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