Skip to main content
Glama

get_workout

Read-onlyIdempotent

Retrieve one Apple Health or Apple Watch workout by ID or file name, including parts, distance, pace, heart rate, zones, pool lengths and effort; optionally add laps and heart-rate series.

Instructions

One session in full: every part with its label, distance, pace and heart rate (also as parts_text lines you can quote), zone seconds, pool lengths with stroke and SWOLF, recovery heart rate, the athlete's effort and feel, cardiac cost. Heart-rate series only if you ask.

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": {
      "id": "<id>"
    },
    "name": "get_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWorkout id (full UUID or its first 8 characters) or file name.
include_lapsNoInclude pool lengths. Default true.
include_hr_seriesNoInclude the heart-rate series (about one sample every 5 s). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and idempotentHint, so safety is covered; the description adds genuinely useful behavioral context about what is returned (quotable parts_text lines, zone seconds, SWOLF, cardiac cost) and that HR series is conditional. It does not state response size or cost, which is the main remaining gap for a potentially large payload.

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?

It is a single front-loaded sentence that leads with "One session in full" before the field list, and the trailing clause about HR series is a sensible qualifier. The dense comma-list of return fields is long but each item conveys concrete content, so little is wasted.

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?

With no output schema, the description carries the burden of describing the return shape and does so thoroughly across workout parts, zones, pool lengths, and cardiac metrics. The omissions are minor: no error behavior for a bad id and no indication of payload size.

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 description coverage is 100%, so all three parameters (id, include_laps, include_hr_series) are already documented, making the baseline 3. The description reinforces the conditional nature of the heart-rate series but says nothing about include_laps or the id format beyond what the schema already states.

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?

"One session in full" plus an enumeration of the returned data (parts, labels, distance, pace, heart rate, zones, pool lengths, SWOLF, recovery HR) makes it clear this is a detailed single-workout retrieval by id. It is distinguishable from list-type siblings like list_workouts by the word "One," though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

The phrase "Heart-rate series only if you ask" hints that the heavy data is opt-in, which implicitly guides invocation. However, there is no explicit when-to-use vs. when-to-use-a-sibling guidance, and no mention of what to do if the id is unknown or that list_workouts should be called first to find an id.

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