mcp-google-health

export_exercise_tcx

Read-only

Export one exercise as TCX with GPS track, heart rate, and laps; provide an output path to save the file or return TCX text directly.

Instructions

Export one exercise as TCX with GPS track, heart rate, and laps. Needs the location scope. Give outputPath to save the file instead of returning the TCX text.

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": {
      "exerciseId": "<exerciseId>"
    },
    "name": "export_exercise_tcx"
  }
}

Input Schema

Name	Required	Description
`exerciseId`	Yes	The exercise data point ID.
`outputPath`	No	File path for the TCX file.
`partialData`	No	Include data points when the exercise has no GPS data.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.8/5.0

Behavior1/5

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

The annotations declare readOnlyHint=true, but the description says outputPath saves a file, which is an environment write and contradicts the read-only annotation. Other useful behavior is disclosed, but the contradiction requires a score of 1.

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 tight sentences, front-loaded with the purpose and output format. The prerequisite and outputPath behavior are stated without unnecessary wording.

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 three-parameter export tool with no output schema, the description explains what is returned and how outputPath changes it. It omits overwrite and error behavior for file saving, but the essential invocation context is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3. The description adds meaningful semantics for outputPath by explaining that it changes the return behavior from TCX text to a saved file; it does not explain partialData beyond the schema.

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 states a specific verb and resource: export one exercise as TCX. It enumerates included content (GPS track, heart rate, laps), making it clearly distinct from sibling data-point CRUD tools.

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?

It gives a clear prerequisite (location scope) and explains the outputPath mode: save a file instead of returning TCX text. It does not name an explicit alternative or when-not-to-use case, but the intended use is unambiguous.

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