Skip to main content
Glama
google-health-mcp

google-health-mcp

health_get_exercise_route

Retrieve an exercise's GPS route as a TCX file by log_id, optionally including the full trackpoint data when needed.

Instructions

Get the GPS route of one exercise, as the TCX file Google exports.

Only exercises recorded with GPS have a route, and a sync fetches routes for the workouts in its own window. The TCX text carries every trackpoint (time, position, altitude, distance, heart rate) and can run to hundreds of kilobytes, so it is returned only when asked for.

Args: log_id: The exercise's log_id, as health_get_exercises returns it. include_tcx: If true, include the TCX text itself.

Returns the exercise's log_id, date and provider, and the TCX text when asked for.

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": {
      "log_id": "<log_id>"
    },
    "name": "health_get_exercise_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
log_idYes
include_tcxNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.12.0
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "health_get_exercise_routeOutput",
      -  "type": "object"
      -}New value: +null
  2. Addedv1.7.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses the potentially huge payload (hundreds of kilobytes of trackpoints) and the opt-in include_tcx gate that keeps the default response small. It omits any statement of error behavior or what a null route looks like, which is the remaining gap.

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?

Front-loaded with the core purpose, then prerequisites, then cost rationale — a strong ordering. Mild redundancy: 'returned only when asked for' is restated in the Args and Returns sections, and the docstring-style Args/Returns blocks duplicate content already implied by the prose.

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?

Covers prerequisites, return contents (log_id, date, provider, optional TCX), and the size caveat — everything needed to call it correctly for a 2-param read tool with no annotations or output schema. Minor gap: no mention of behavior when the exercise has no GPS route despite the precondition being stated.

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

Parameters5/5

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

Schema coverage is 0%, yet both parameters are fully explained: log_id is explicitly tied to health_get_exercises output, and include_tcx is explained with its consequence (full trackpoint text, large payload). This is meaning the schema does not provide anywhere.

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?

States a specific verb and resource — 'Get the GPS route of one exercise' — and pins the format ('as the TCX file Google exports'). The scoping clause 'Only exercises recorded with GPS have a route' distinguishes it from health_get_exercises and other health_get_* siblings without needing the schema.

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?

Gives clear preconditions (must be GPS-recorded, routes are fetched by a sync within its own window) and points at the log_id source by naming health_get_exercises. However, it never explicitly says 'use X instead when you only need summary data' or what to do when no route exists.

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