Skip to main content
Glama
Sign In
Google Health MCP

Google Health MCP

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Google Health Agent Manifest

google_health_agent_manifest
Read-onlyIdempotent

Provides machine-readable install and runtime guidance for AI agents, enabling correct client setup without calling Google Health or exposing secrets.

Instructions

Machine-readable install, runtime and client guidance for AI agents. Does not call Google Health or expose 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_agent_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientNogeneric
response_formatNomarkdown

Output Schema

NameRequiredDescriptionDefault
linksYes
oauthYes
clientYesgeneric
hermesYes
statusYes
packageYes
projectYes
mcp_nameYes
resourcesYes
unofficialYes
agent_rulesYes
beta_noticeYes
mutating_toolsYes
standard_toolsYes
troubleshootingYes
recommended_first_callsYes

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. Changed2 schema fields changedv0.5.1
    • addedOutput schema / properties / mutating_tools
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "enabled": {
+      "type": "boolean"
+    },
+    "policy": {
+      "type": "string"
+    },
+    "scope_preset": {
+      "type": "string"
+    },
+    "write_scope": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "enabled",
+    "write_scope",
+    "scope_preset",
+    "policy"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "project",
-  "mcp_name",
-  "client",
-  "unofficial",
-  "status",
-  "beta_notice",
-  "package",
-  "oauth",
-  "recommended_first_calls",
-  "standard_tools",
-  "resources",
-  "hermes",
-  "agent_rules",
-  "troubleshooting",
-  "links"
-]New value: +[
+  "project",
+  "mcp_name",
+  "client",
+  "unofficial",
+  "status",
+  "beta_notice",
+  "package",
+  "oauth",
+  "recommended_first_calls",
+  "standard_tools",
+  "resources",
+  "mutating_tools",
+  "hermes",
+  "agent_rules",
+  "troubleshooting",
+  "links"
+]
  3. First observedv0.1.3

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already indicate the tool is read-only, idempotent, and non-destructive. The description adds meaningful safety-relevant behavior beyond annotations: it does not call Google Health and does not expose secrets. This is useful context for an agent deciding whether invoking the tool is safe.

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, front-loaded sentence with no filler. Both clauses earn their place: one defines the resource, the other clarifies important boundaries regarding external calls and secrets.

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?

This is a low-complexity tool with two optional enum parameters, an existing output schema, and strong safety annotations. The description adequately conveys the tool's purpose and its non-action boundaries. It does not detail output structure, but that is covered by the output schema.

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?

Schema description coverage is 0%, and the description does not explain either parameter. The client and response_format enums are fairly self-explanatory from their names and allowed values, but the description fails to compensate for the complete lack of schema-level descriptions.

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 the tool provides 'machine-readable install, runtime and client guidance for AI agents,' identifying a clear resource and purpose. It also distinguishes itself by explicitly noting it does not call Google Health or expose secrets, though it does not name specific sibling tools.

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 'install, runtime and client guidance' implies the tool is meant for agent setup and configuration, but there is no explicit when-to-use guidance or comparison to alternatives like google_health_quickstart or google_health_onboarding. The intended usage must be inferred rather than stated.

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

Deploy Server

Other Tools