mcp-google-health

list_paired_devices

Read-only

List a user's paired health devices with battery level, status, firmware, features, and last sync time to check device readiness and sync status.

Instructions

List the user's paired devices with battery level, battery status, firmware version, features, and last sync time.

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": "list_paired_devices"
  }
}

Input Schema

Name	Required	Description	Default
`pageSize`	No
`pageToken`	No	nextPageToken from the previous response.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by naming the fields returned, which matters since there is no output schema, but it says nothing about pagination behavior or how results are ordered.

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; the resource is named first and the returned fields follow. It is efficiently sized, though the trailing field list reads as a dump rather than structured guidance.

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?

For a simple two-parameter read tool with no output schema, the description covers what comes back, which is the main gap it needed to fill. It omits pagination mechanics and the pageSize default, leaving an agent to guess how to page through large device lists.

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?

The description mentions neither parameter. With only 50% schema description coverage, pageSize has no documented meaning, default, or interaction with pageToken anywhere, so the description fails to compensate for the gap.

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 and resource ("List the user's paired devices") and enumerates the data returned (battery level, status, firmware, features, last sync). It does not distinguish itself from the sibling get_paired_device, which an agent must infer returns a single device.

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 explicit when-to-use guidance, no mention of when to prefer get_paired_device for a single device, and no prerequisites or rate/permission notes. Usage is only implied by the verb "List".

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