Skip to main content
Glama
google-health-mcp

google-health-mcp

by BIGDaddy504

Workout GPS route

get_exercise_route
Read-only

Retrieve a GPS workout route as a privacy-protected summary or map points by exercise id, with start/finish hidden; workouts without GPS return no route.

Instructions

Route of one GPS workout. By default returns only a summary with no coordinates: distance, duration, elevation gain and heart rate. Set maxPoints only when the user wants to see the route on a map; points near the start and finish are always hidden for privacy, because they usually reveal where the user lives. Get the exercise id from get_data_points with dataType 'exercise'. Workouts recorded without GPS have no route.

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": {
      "exercise": "<exercise>"
    },
    "name": "get_exercise_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
exerciseYesExercise id, or the full data point name from get_data_points, e.g. users/123/dataTypes/exercise/dataPoints/456.
maxPointsNoMost track points (time, lat, lon, altitude, heart rate) to return, for drawing the route. Default 0: summary only, no coordinates. Use about 200 for a map.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses non-obvious behavior: summary-only by default, deliberate privacy truncation of points near start and finish, the rationale (they reveal where the user lives), and the empty-result case for non-GPS workouts. These are exactly the traits an agent could not infer from annotations.

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?

Five short sentences, front-loaded with the default return shape before the maxPoints caveat and the prerequisite. Slightly dense but every clause carries actionable information; nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so: it names the summary fields (distance, duration, elevation gain, heart rate) and explains when coordinate data appears. Combined with the annotations and full schema coverage, an agent can call this correctly without further information.

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 100% and already documents maxPoints including the ~200 suggestion, so the baseline is 3. The description still adds decision-level meaning: it frames maxPoints as a cost/privacy tradeoff gated on map display rather than a raw limit, though it does not add format details for the exercise id.

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?

Opens with a specific verb+resource: 'Route of one GPS workout.' Immediately clarifies the default payload (summary without coordinates) so the agent knows this is not a generic data-point reader, distinguishing it from siblings like get_data_points and get_daily_rollup.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule for maxPoints ('only when the user wants to see the route on a map'), a prerequisite for obtaining the exercise id from get_data_points with dataType 'exercise', and a clear no-op case ('workouts recorded without GPS have no route'). Both the trigger and the non-trigger are stated.

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