Skip to main content
Glama
Google Health MCP — Remote

Google Health MCP — Remote

Google Health Connection Status

google_health_connection_status
Read-onlyIdempotent

Checks local Google Health setup—config, token file, Node version, privacy mode, cache, and optional MCP client readiness—without calling Google APIs or exposing secrets.

Instructions

Check local Google Health config, token file, Node version, privacy mode, cache readiness and optional MCP client readiness without calling Google APIs or exposing secrets.

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

Input Schema

NameRequiredDescriptionDefault
clientNogeneric
response_formatNomarkdown

Output Schema

NameRequiredDescriptionDefault
okYes
nodeYes
cacheYes
oauthYes
tokenYes
clientNogeneric
configYes
headlessYes
next_stepsYes
missing_envYes
privacy_modeYes
redirect_uriNo
required_envYes
client_checksNo
automatic_auth_supportedYes
ready_for_google_health_apiYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: no Google API calls are made and secrets are not exposed, which tells the agent this is safe to run purely for local diagnosis.

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?

A single dense sentence with the resource scope front-loaded and the key constraint (no API calls, no secret exposure) at the end. The comma-separated checklist is efficient, though slightly list-heavy for a one-sentence description.

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?

An output schema exists, so return values need no explanation, and the description covers what is inspected and the offline/secret-safe behavior. The only gap is the unexplained response_format and client enum semantics, which is minor for a zero-required-parameter diagnostic tool.

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 0%, so the description must carry the burden. It partially does by referencing "optional MCP client readiness," which maps to the `client` enum, but it never explains the enum values or the `response_format` parameter at all.

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 gives a specific verb ("Check") and enumerates exactly what is inspected: local config, token file, Node version, privacy mode, cache readiness, and optional MCP client readiness. That scope set separates it from siblings such as google_health_cache_status and google_health_capabilities, though it never names those siblings explicitly.

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 phrase "without calling Google APIs" implies the diagnostic/offline use case, and "optional MCP client readiness" hints that client-specific checks are opt-in. However, there is no explicit statement of when to prefer this over google_health_cache_status or google_health_capabilities, so the agent must infer routing.

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