mcp-google-health

get_data_point

Read-only

Retrieve a single Google Health data point, such as an exercise, sleep session, weight, or log entry, using its data type and resource ID.

Instructions

Get one identifiable data point, such as an exercise, sleep session, weight, or log entry.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataType": "<dataType>",
      "dataPointId": "<dataPointId>"
    },
    "name": "get_data_point"
  }
}

Input Schema

Name	Required	Description
`dataType`	Yes	Data type in kebab case, such as steps, sleep, or heart-rate. See list_data_types.
`apiVersion`	No	API version. Defaults to v4, or v4beta for beta-only data types.
`dataPointId`	Yes	A resource ID without slashes.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond that — no mention of what happens when the ID is unknown, that the response shape varies by data type, or any rate/permission notes.

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?

A single well-formed sentence with the resource front-loaded after the verb; nothing is redundant or padded.

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 three-parameter read tool with full schema documentation and no output schema, the description is minimally adequate. It leaves out how the agent should obtain a dataPointId and what the varied return payloads look like, which would matter for an open-world read.

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 coverage is 100%, so dataType, apiVersion, and dataPointId are all documented in the schema, including the pointer to list_data_types. The description's examples loosely map to dataType values but add no format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Get') and resource ('one identifiable data point') and enumerates concrete examples (exercise, sleep session, weight, log entry) that make the returned entity type clear. It does not distinguish itself from siblings like list_data_points or daily_roll_up_data_points, so an agent must infer that this is the single-item fetch.

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?

No when-to-use guidance is given: nothing says to use this when you already have a data point ID, nor that list_data_points should be used to discover IDs first. The word 'identifiable' hints that an ID is required, but that is about as far as the guidance goes.

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