Skip to main content
Glama

get_workout_detail

Read-onlyIdempotent

Get the full structured detail of one workout template by its workout_id: exercise display names, sets, loads, rest modes, supersets, RPE, and percentages of training max, plus its folder. Returns the workout in the workouts array, or an empty array when no workout has that id.

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": {
      "workout_id": "<workout_id>"
    },
    "name": "get_workout_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
workout_idYesThe workout's workout_id, as a tool result lists it

Output Schema

NameRequiredDescriptionDefault
workoutsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / workout_id / description
      Previous value: -"Stable id of the saved workout"New value: +"The workout's workout_id, as a tool result lists it"
    • addedInput schema / properties / workout_id / minLength
      Added value: +1
    • removedInput schema / properties / workout_name
      Removed value: -{
      -  "description": "The exact name of the workout template",
      -  "type": "string"
      -}
    • addedInput schema / required
      Added value: +[
      +  "workout_id"
      +]
    • addedOutput schema / properties / workouts / items / properties / folder_id
      Added value: +{
      +  "description": "The folder that holds the workout; absent when it is in no folder.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / workouts / items / properties / workout_id
      Added value: +{
      +  "description": "Names this workout in every tool that takes a workout_id.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / workouts / items / required
      Previous value: -[
      -  "name",
      -  "exercises"
      -]New value: +[
      +  "workout_id",
      +  "name",
      +  "exercises"
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / workouts / items / properties / exercises / items / properties / wait_for_lap_after
      Added value: +{
      +  "description": "True when the watch waits for a lap button press after this exercise, before the next one.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / workouts / items / properties / warmup
      Added value: +{
      +  "description": "True when the workout starts with an open warmup step on the watch.",
      +  "type": "boolean"
      +}
  3. Changed2 schema fields changed
    • removedInput schema / properties / workout_id / minLength
      Removed value: -1
    • removedInput schema / properties / workout_name / minLength
      Removed value: -1
  4. Changed1 schema field changed
    • changedInput schema / properties / workout_id / description
      Previous value: -"Stable workout id returned by another LiftTrack tool"New value: +"Stable id of the saved workout"
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuine behavioral context beyond that: the workout is returned inside a 'workouts' array and an empty array is returned when the id matches nothing, which tells the agent how to handle a miss.

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?

Front-loaded with the verb and resource, then the field inventory, then the return/not-found behavior. No filler or redundant sentences; every clause either scopes the lookup or describes output.

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 single-entity read with a full input schema and an output schema, the description covers identity, payload and missing-record behavior. Only the relationship to the listing tool (whether to call get_workout_templates first to obtain the id) is left unstressed.

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?

The single parameter has 100% schema description coverage ('the workout's workout_id, as a tool result lists it'), so the schema carries the meaning. The description only restates that lookup is by workout_id without adding format or sourcing detail beyond the schema, which is the expected baseline.

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 full structured detail of one workout template') plus the identifier it keys on, and the phrase 'one workout template' implicitly separates it from the list-style get_workout_templates. The enumerated payload (sets, loads, rest modes, supersets, RPE, % of training max, folder) tells an agent exactly what detail it will receive.

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?

Usage is implied: call it when you have a workout_id and need details. There is no explicit when-to-use consultation of get_workout_templates first, nor any when-not guidance or named alternative, so the agent must infer ordering.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources