Skip to main content
Glama
davidmosiah

Google Health MCP

by davidmosiah
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

Google Health Cache Status

google_health_cache_status
Read-onlyIdempotent

Check whether the optional local SQLite cache is active for Google Health data. Enable caching with GOOGLE_HEALTH_CACHE=sqlite or true, then verify status here.

Instructions

Show optional local SQLite cache status. Enable with GOOGLE_HEALTH_CACHE=sqlite or GOOGLE_HEALTH_CACHE=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
enabledYes
entriesYes
http_cacheNo
newest_cached_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.7
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv0.7.3
  3. Removedv0.5.3
  4. Changed1 schema field changedv0.5.1
    • addedOutput schema / properties / http_cache
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "bypass_env_var": {
+      "type": "string"
+    },
+    "default_ttl_seconds": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "hit_count": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "hit_rate": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "miss_count": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "size": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "size",
+    "hit_count",
+    "miss_count",
+    "hit_rate",
+    "default_ttl_seconds",
+    "bypass_env_var"
+  ],
+  "type": "object"
+}
  5. First observedv0.1.3

TDQS

A4/5.0
Behavior4/5

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

Annotations already signal readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable context beyond those: the cache is optional and local SQLite, and it names the environment variables that turn it on. It does not detail the exact status fields, but the output schema exists and the read-only safety profile is well covered by annotations.

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?

Two short sentences contain all the core information: what the tool shows and how the optional cache is enabled. There is no fluff, and the primary function is front-loaded. Every word earns its place.

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?

For a simple read-only status tool, the description plus rich annotations and an output schema is largely sufficient. The main missing piece is explicit routing among the many sibling health-status tools, but that gap is mostly captured under usage guidelines rather than contextual completeness.

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?

The description does not mention response_format, and schema description coverage is 0%. However, the input schema fully documents the only parameter through its enum (markdown/json) and default value (markdown), making the parameter's meaning self-sufficient. The description misses a chance to compensate for the lack of schema descriptions, but the agent will not be confused about how to invoke the tool.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Show optional local SQLite cache status.' The term 'cache status' clearly distinguishes it from siblings like google_health_connection_status, google_health_data_inventory, and google_health_capabilities. An agent can tell exactly what this tool does without guessing.

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 description provides useful enablement context: 'Enable with GOOGLE_HEALTH_CACHE=sqlite or GOOGLE_HEALTH_CACHE=true.' However, it never explicitly states when to use this tool versus alternatives, nor does it name any sibling as a better choice for other kinds of status checks. Usage is implied but not explicit.

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

Install Server

Other Tools