Skip to main content
Glama
Google Health MCP — Remote

Google Health MCP — Remote

Google Health Weekly Review

google_health_weekly_summary
Read-onlyIdempotent

Generate a weekly Google Health scorecard covering activity, sleep, and heart context, with missing-data awareness for read-only, non-medical review.

Instructions

Build a weekly Google Health scorecard with activity, sleep, heart context and missing-data awareness. 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_weekly_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoRecent analysis window in days.
timezoneNoIANA timezone used to resolve "today" and the day windows, e.g. America/New_York. Defaults to the profile timezone, then UTC.
compare_daysNoPrior comparison window in days. Use 0 to disable comparison.
response_formatNomarkdown

Output Schema

NameRequiredDescriptionDefault
kindYes
generated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is largely covered. The description adds useful context with "beta, non-medical" and "missing-data awareness," but it repeats read-only and does not explain auth requirements, rate limits, or what the scorecard returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence with the purpose and caveats front-loaded. It contains no filler or redundant wording.

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 and rich annotations reduce the description's burden, and the description covers the scorecard domains plus beta/non-medical caveats. However, for a tool in a crowded sibling set, it does not explain how windows and comparison work or when to choose it over nearby summary tools.

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

Parameters3/5

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

Schema description coverage is 75%, so most parameters are already documented in the schema. The description does not mention days, timezone, compare_days, or response_format, so it adds no parameter meaning beyond the schema; baseline 3 is appropriate.

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 description states a specific verb and resource: "Build a weekly Google Health scorecard." It names included domains (activity, sleep, heart context) and a scope qualifier (weekly), but it does not explicitly distinguish this from siblings such as google_health_daily_summary or google_health_rollup.

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 explicit when-to-use or when-not-to-use guidance, and no alternative sibling is named. The word "weekly" implies a cadence, but an agent must infer when this scorecard is preferable to daily_summary, rollup, or wellness_context.

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