Skip to main content
Glama
Google Health MCP — Remote

Google Health MCP — Remote

Google Health Wellness Context

google_health_wellness_context
Read-onlyIdempotent

Converts Google Health activity and sleep data into a shared wellness_context format so recommendation engines can use it for personalized health suggestions.

Instructions

Normalize Google Health activity/sleep context into the shared wellness_context shape for recommendation engines.

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

Input Schema

NameRequiredDescriptionDefault
daysNoCurrently unused: the context is built from today's summary only.
notesNo
sorenessNo
timezoneNoIANA timezone used to resolve "today" and the day windows, e.g. America/New_York. Defaults to the profile timezone, then UTC.
injury_flagsNo
response_formatNomarkdown

Output Schema

NameRequiredDescriptionDefault
notesYes
sourceYes
sorenessYes
generated_atYes
injury_flagsYes
recent_training_loadYes

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 establish a read-only, idempotent, non-destructive, open-world operation. The description adds source-domain and normalization scope, but it does not disclose that the context is built from today's summary only or explain authentication and timezone fallback behavior; the current-day limitation appears only in 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.

Conciseness5/5

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

The single sentence is front-loaded with the action and efficiently communicates the source, output shape, and intended consumer without filler. Its omissions are completeness gaps rather than problems with wording or structure.

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?

The output schema covers the return contract, the annotations cover safety, and the absence of required parameters makes a basic invocation straightforward. However, limited parameter documentation and the lack of current-day behavioral context or sibling-selection guidance leave noticeable gaps for confident use.

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?

With only 33% schema description coverage, the description needed to compensate but explains none of the six parameters. In particular, it does not clarify how notes, soreness, and injury_flags supplement the Google Health data, while the useful current-day and timezone-fallback semantics remain confined to the schema.

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 supplies a specific operation ("Normalize"), source scope ("Google Health activity/sleep context"), and target ("shared wellness_context shape"), along with the downstream consumer. It does not explicitly distinguish the tool from the daily/weekly summary or rollup siblings, so it falls short of a 5.

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?

"For recommendation engines" implies the intended use case, but there is no explicit guidance on when to choose this over google_health_daily_summary, google_health_weekly_summary, or google_health_rollup. No prerequisites or when-not conditions are provided.

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