Skip to main content
Glama
Google Health MCP — Remote

Google Health MCP — Remote

Google Health Privacy Audit

google_health_privacy_audit
Read-onlyIdempotent

Audit local privacy, cache, token-path, and environment-presence posture without revealing secret values.

Instructions

Return local privacy, cache, token-path and env-presence posture without revealing secret values.

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

Input Schema

NameRequiredDescriptionDefault
response_formatNomarkdown

Output Schema

NameRequiredDescriptionDefault
notesYes
projectYes
cache_pathYes
token_pathYes
unofficialYes
stdout_safeYes
cache_reasonNo
cache_enabledYes
config_sourceYes
secret_env_varsYes
cache_configuredNo
gps_redacted_keysYes
local_config_pathYes
local_config_existsYes
raw_payloads_opt_inYes
privacy_mode_defaultYes
required_env_presentYes
gps_redaction_defaultYes
redacted_key_patternsYes
gps_redacted_container_keysYes
local_config_secure_permissionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3/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=false, so the safety profile is fully covered structurally. The description adds one genuinely new behavioral guarantee beyond that: secret values are never revealed, only presence is reported. It does not say what checks are performed, whether the audit touches the filesystem or network, or how findings are classified.

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 front-loaded sentence with no filler, and the redaction guarantee is placed where it matters most. It is efficient, though the density of four comma-separated audit targets in one clause makes it slightly harder to scan than it could be.

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 no explanation, and the tool is a parameter-free read-only audit. However, 'posture' is never unpacked, so an agent cannot predict what findings or severities come back or what to do with them, which is a real gap for a diagnostic tool.

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?

There is one parameter, response_format, with an enum of markdown/json and a default, and schema description coverage is 0%. The description never mentions output format selection, so it does not compensate for the coverage gap. The enum values are largely self-explanatory, which keeps this from being a 1.

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 uses a specific verb ('Return') and enumerates the resources audited: local privacy, cache, token-path and env-presence posture. That distinguishes it from read-only siblings like google_health_cache_status and google_health_connection_status, which cover narrower slices. It stops short of 5 because 'posture' is abstract and the tool's relationship to those siblings is not stated.

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 mention of when to prefer google_health_cache_status or google_health_connection_status instead, and no prerequisites or exclusions. An agent must infer that this is a pre-flight or diagnostic check from the word 'audit' alone.

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