Skip to main content
Glama

update_workout

DestructiveIdempotent

Change an existing workout template. workout_id names the workout and workout_name is its current name, which must match. Folder membership is never changed. Omitted fields keep their current values.

name renames the workout. exercises replaces the entire exercise list, including all exercises and sets to retain. Progression links are preserved for exercises that keep their name. Each exercise uses an exact catalog or custom exercise display name, target (reps|time), load (weight|percent), working sets, and rest configuration, with optional warmup sets, supersets, RPE, and notes. The input schema defines the fields and constraints. Notes appear on the watch in the workout step description.

warmup turns the open warmup step at the start on or off; omitted, it stays as it is. Per exercise wait_for_lap_after: omitted, an exercise that was already in the workout keeps its value and a newly added exercise gets the user's workout settings. Pass either only when the user asked to change it. The result reports the final warmup and wait_for_lap_count.

A rename-only request contains workout_id, workout_name and name; it does not require exercises.

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>",
      "workout_name": "<workout_name>"
    },
    "name": "update_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name for the workout (a rename)
warmupNoTurn the open warmup step at the start of the workout on or off. Omit to leave it as it is; pass it only when the user asked to change it. Adds one step.
exercisesNoFull replacement exercise list, including all exercises and sets to retain. Exercises absent from this array are removed. Omission of this field preserves the existing exercise list. The workout must fit within 100 steps: each warmup or working set counts as one step, plus one for each timed or lap rest, one for the workout warmup and one for each wait for lap after an exercise. Off rests add no steps.
workout_idYesThe workout's workout_id, as a tool result lists it
workout_nameYesThe workout's current name, as its tool result lists it. Checked against workout_id; a mismatch is refused.

Output Schema

NameRequiredDescriptionDefault
nameYesFinal workout name after the update
warmupYesFinal state: the workout starts with the open warmup step
updatedYesWhich slices were written
set_countYes
workout_idYes
previous_nameNoPresent only when the name actually changed
exercise_countYes
wait_for_lap_countYesFinal state: exercises followed by a wait for the lap button, including any the user's workout settings added to newly added exercises

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / workout_folder_name
      Removed value: -{
      -  "description": "Folder of the target workout, only needed when several workouts share the name. Identity only: this tool never moves a workout between folders.",
      -  "minLength": 1,
      -  "type": "string"
      -}
    • addedInput schema / properties / workout_id
      Added value: +{
      +  "description": "The workout's workout_id, as a tool result lists it",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / workout_name / description
      Previous value: -"Exact current name of the workout to update"New value: +"The workout's current name, as its tool result lists it. Checked against workout_id; a mismatch is refused."
    • changedInput schema / required
      Previous value: -[
      -  "workout_name"
      -]New value: +[
      +  "workout_id",
      +  "workout_name"
      +]
    • addedOutput schema / properties / workout_id
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "name",
      -  "exercise_count",
      -  "set_count",
      -  "updated",
      -  "warmup",
      -  "wait_for_lap_count"
      -]New value: +[
      +  "workout_id",
      +  "name",
      +  "exercise_count",
      +  "set_count",
      +  "updated",
      +  "warmup",
      +  "wait_for_lap_count"
      +]
  2. Changed7 schema fields changed
    • changedInput schema / properties / exercises / description
      Previous value: -"Full replacement exercise list, including all exercises and sets to retain. Exercises absent from this array are removed. Omission of this field preserves the existing exercise list. The workout must fit within 100 steps: each warmup or working set counts as one step, plus one for each timed or lap rest. Off rests add no steps."New value: +"Full replacement exercise list, including all exercises and sets to retain. Exercises absent from this array are removed. Omission of this field preserves the existing exercise list. The workout must fit within 100 steps: each warmup or working set counts as one step, plus one for each timed or lap rest, one for the workout warmup and one for each wait for lap after an exercise. Off rests add no steps."
    • addedInput schema / properties / exercises / items / properties / wait_for_lap_after
      Added value: +{
      +  "description": "Whether the watch waits for a lap button press after this exercise's last set and rest, before the next exercise. Omit to apply the user's workout settings; pass it only when the user asked for something different in this request. Has no effect on the last exercise, on an exercise followed by another member of its superset, or when working_rest_mode is 'lap'. Adds one step.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / warmup
      Added value: +{
      +  "description": "Turn the open warmup step at the start of the workout on or off. Omit to leave it as it is; pass it only when the user asked to change it. Adds one step.",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / updated / items / enum
      Previous value: -[
      -  "name",
      -  "exercises"
      -]New value: +[
      +  "name",
      +  "exercises",
      +  "warmup"
      +]
    • addedOutput schema / properties / wait_for_lap_count
      Added value: +{
      +  "description": "Final state: exercises followed by a wait for the lap button, including any the user's workout settings added to newly added exercises",
      +  "type": "number"
      +}
    • addedOutput schema / properties / warmup
      Added value: +{
      +  "description": "Final state: the workout starts with the open warmup step",
      +  "type": "boolean"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "name",
      -  "exercise_count",
      -  "set_count",
      -  "updated"
      -]New value: +[
      +  "name",
      +  "exercise_count",
      +  "set_count",
      +  "updated",
      +  "warmup",
      +  "wait_for_lap_count"
      +]
  3. Changed4 schema fields changed
    • changedInput schema / properties / exercises / description
      Previous value: -"Full replacement exercise list, including all exercises and sets to retain. Exercises absent from this array are removed. Omission of this field preserves the existing exercise list."New value: +"Full replacement exercise list, including all exercises and sets to retain. Exercises absent from this array are removed. Omission of this field preserves the existing exercise list. The workout must fit within 100 steps: each warmup or working set counts as one step, plus one for each timed or lap rest. Off rests add no steps."
    • removedInput schema / properties / exercises / items / properties / warmup_sets / maxItems
      Removed value: -10
    • removedInput schema / properties / exercises / items / properties / working_sets / maxItems
      Removed value: -10
    • changedInput schema / properties / exercises / maxItems
      Previous value: -12New value: +100
  4. Changed3 schema fields changed
    • changedInput schema / properties / exercises / description
      Previous value: -"Full replacement exercise list. Read the workout with get_workout_detail first, edit the returned object, and pass the COMPLETE array back, including exercises you are not changing."New value: +"Full replacement exercise list, including all exercises and sets to retain. Exercises absent from this array are removed. Omission of this field preserves the existing exercise list."
    • changedInput schema / properties / exercises / items / properties / name / description
      Previous value: -"Exact name from search_exercises"New value: +"Exact display name from the exercise catalog or the user's custom exercises"
    • changedInput schema / properties / exercises / items / properties / warmup_sets / items / properties / percent / description
      Previous value: -"Percent of training max, e.g. 70 for 70% — required when the exercise load is percent. Pass the percentage, not a computed weight."New value: +"Percent of training max, e.g. 70 for 70%, not a computed weight — required when the exercise load is percent."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive and idempotent, and the description adds the crucial semantics that drive those hints: exercises is a full replacement whose absent entries are removed, progression links survive renames, folder membership is untouched, and a workout_name mismatch is refused. This is exactly the context an agent needs before a destructive overwrite.

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 mutation semantics, then per-field rules, then the minimal rename case — a sensible ordering with no filler paragraphs. It is somewhat verbose and repeats schema-only details, which keeps it from a 5.

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?

Annotations cover safety, an output schema covers return values, and the description covers the remaining cognitive load: replacement vs preservation, defaults for omitted fields, and the shortcut for a pure rename. Nothing needed to invoke it correctly is missing.

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%, so baseline is 3; the description earns above that by explaining cross-field relationships the schema states only in fragments — the rename-only minimal payload and the rule that new vs retained exercises get different wait_for_lap_after defaults. Some sentences merely restate schema text (notes appearing on the watch).

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 and resource ('Change an existing workout template') and immediately scopes what is and is not mutable (fields yes, folder membership never). An agent can distinguish this from create_workout or delete_workout from the first sentence.

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 strong conditional guidance: omitted fields keep current values, warmup/wait_for_lap_after should be passed 'only when the user asked to change it', and a rename-only request needs just three fields. It stops short of naming sibling alternatives (create_workout, schedule_workout) for parallel intent routing, so it is a 4 rather than a 5.

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