Google Health MCP

Overview Schema Source Related Servers Score Discussions Admin

Get Google Health OAuth URL

google_health_get_auth_url

Read-onlyIdempotent

Generate a Google OAuth authorization URL for Google Health API access when no local token exists. Use this first step to obtain user consent and retrieve an authorization code.

Instructions

Generate a Google OAuth authorization URL for Google Health API. Use this first when no local token exists.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`state`	No	Optional OAuth state value generated by the caller.
`scopes`	No	Optional scope override. Defaults to read-only Google Health scopes used by this server.
`response_format`	No		markdown

Output Schema

TableJSON Schema

Name	Required	Description
`scopes`	Yes
`auth_url`	Yes
`next_step`	Yes
`redirect_uri`	Yes
`code_verifier`	Yes	PKCE code verifier. Pass this to google_health_exchange_code.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.7.7Aug 29, 2026

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"

addedOutput schema / properties / code_verifier

Added value: +{
+  "description": "PKCE code verifier. Pass this to google_health_exchange_code.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "auth_url",
-  "redirect_uri",
-  "scopes",
-  "next_step"
-]New value: +[
+  "auth_url",
+  "redirect_uri",
+  "scopes",
+  "code_verifier",
+  "next_step"
+]

First observedv0.1.3May 7, 2026

TDQS

A4/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which fully cover the safety profile. The description adds no additional behavioral detail, but it also does not contradict the annotations, so a baseline score is appropriate.

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 sentences with no wasted words. The core purpose is front-loaded, and the usage condition is stated immediately after, making the description easy to parse and act on.

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 zero-required-parameter tool with an output schema and safety annotations, the description is nearly complete: it states what the tool does and when to call it. It could optionally mention the next step of exchanging the code, but that is inferable from the sibling tool list.

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 67%, with state and scopes already documented in the schema and response_format having an enum and default. The description does not add parameter-level meaning, but the schema carries most of the semantic weight. This is adequate but not enhanced.

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 clearly states the verb 'Generate' and the specific resource: a Google OAuth authorization URL for the Google Health API. This distinguishes it from sibling tools like google_health_exchange_code or google_health_connection_status, which handle different steps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use this tool first when no local token exists, providing a clear condition and ordering. It does not explicitly name alternatives or when-not-to-use scenarios, but the condition is specific enough for an agent to route correctly.

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