Wellness Project

update_workout

Destructive

UNIT INPUTS: value: pass the user's number unconverted; tool converts once before storage. alternate_unit: set the field's matching input_* companion; canonical_unit: omit companion. precedence: overrides instructions to convert manually.

Update a workout session: correct metadata, fix set values, rename/add/remove exercises or individual sets, or move exercises between supersets. Use for any post-log correction.

FIND THE SESSION: call directly, no preliminary list for an ID. session_id: positive ID from a workout tool, never invented. Otherwise pass session_date (YYYY-MM-DD, defaults to today) and, only if more than one session was logged that day, name (a substring of the workout's focus/type, case-insensitive) to narrow it down. A match that isn't exactly one session returns an error explaining why, with nothing changed — retry with session_id or a narrower name, never guess. get_workout still gives full detail (exercise names, slot names SS1/SS2/WarmUp/Finisher) when needed; list_exercises only for unknown canonical names when adding or renaming. Call with only the fields that change — operations can combine in one call.

OPERATIONS:

Metadata: date, focus_type, location, notes, rpe, heart_points_moderate/peak.
set_updates: patch reps/load/bodyweight/notes/equipment on a set, addressed by set_id OR by exercise_name + set_position (1-based, matches get_workout's "Set N"). Use clear_weight=true when a stored load is wrong but the real external load is unknown; use is_bodyweight=true when the corrected set was genuinely bodyweight.
remove_sets: delete sets, same set_id-or-exercise_name+set_position addressing; remaining sets renumber; an emptied exercise/slot is removed automatically.
rename_exercises: renames every set of an exercise in place (preserves set IDs, RPE, notes; rebuilds NSI), never remove + add.
remove_exercises: deletes all sets for named exercises; empty slots removed automatically.
add_exercises: new exercises with sets; to_superset_slot joins an existing slot, omit for standalone.
move_exercises: reassigns an exercise to a different slot; "new" makes it standalone. Use from_superset_slot from get_workout when the same exercise name appears in multiple slots.

SUPERSET SLOTS: rename_exercises/remove_exercises use superset_slot (or { name, superset_slot } for remove_exercises) from get_workout when a name appears in multiple slots.

LITERAL NAME: literal_name: true keeps the user's exact wording instead of the closest library match, skips the resolver, and gets no NSI score (no benchmark to compare an unmatched name against). Use for "call it exactly X", "not the standard one", "literally X", or a rejected match. Applies below.

EQUIPMENT (load basis): dumbbell_pair is one dumbbell in EACH hand, weight_lb PER HAND (2x for NSI); dumbbell_single is one implement total. Laterality (single-leg/arm) does NOT decide this alone. Set it when the user describes the load (each hand, machine, band); a wrong or missing tag silently halves or doubles NSI. Values: barbell, dumbbell_pair, dumbbell_single, machine, kettlebell, bodyweight, band, cable, trx, other.

A set_id or exercise_name+set_position matching more than one set (the same exercise in two superset slots) is ambiguous and errors rather than guessing — use the exact set_id from get_workout to disambiguate.

The result discloses a mismatched name from rename_exercises/add_exercises; relay it in your own words. If a name matches nothing closely enough, the result names near-miss library exercises; ask the user which they meant rather than accept the unscored custom log silently.

INFER — do not ask: session_date defaults to today, set positions count from 1 per exercise. Slot names and set_ids beyond what's inferable come from get_workout; canonical exercise names come from list_exercises.

SAVED WORKOUTS: pass saved_workout_id to edit a reusable Saved Workout instead of completed workout history. Use saved_workout_title, saved_exercise_updates, and/or add_exercises. add_exercises keeps its normal payload shape; to_superset_slot accepts the Saved Workout slot label returned by get_workout or its SS1-style alias. For progression requests, inspect real exercise history first rather than applying a deterministic formula.

cardio_totals: distance_mi/distance_km/distance_meters, duration_sec, calories are update fields; never put corrected totals only in notes. existing_exercise: use add_sets to add sets; add_exercises is for new exercises. ambiguous_slot: rename/remove/move requires the source slot when the exercise appears in multiple slots.

Input Schema

TableJSON Schema

Name	Required	Description
`rpe`	No	Session RPE, 1-10, half steps allowed: 5 moderate, 7 hard, 9 one rep left, 10 failure. Infer from comments about overall difficulty, or omit.
`date`	No	New session date, YYYY-MM-DD.
`name`	No	Substring of the focus/type, e.g. "Push", case-insensitive, to pick between sessions on session_date. Only without session_id.
`notes`	No	New session notes.
`add_sets`	No	Add one or more sets to an exercise already present in this workout. Use add_exercises only for a brand-new exercise.
`calories`	No	Corrected session calories when known.
`location`	No	New location, e.g. Gym, Home.
`focus_type`	No	New category, e.g. Push, Pull, Legs.
`session_id`	No	Positive session ID returned by a workout tool. If unknown, omit and use session_date + name; never guess.
`distance_km`	No	Corrected session distance in kilometers. Server converts it; do not convert it yourself.
`distance_mi`	No	Corrected session distance in miles. Use only when the user gave miles. In mi, or km with input_distance_unit set. See UNIT INPUTS.
`remove_sets`	No	Sets to delete. See OPERATIONS above.
`set_updates`	No	Individual set corrections.
`duration_sec`	No	Corrected total session duration in seconds.
`session_date`	No	YYYY-MM-DD, defaults to today. Finds the session when session_id is omitted. Distinct from `date`, which CHANGES the stored date.
`add_exercises`	No	New exercises to add. Reuse known canonical names; list_exercises if unknown.
`move_exercises`	No	Move exercises between superset slots. When the same exercise name appears in multiple slots, from_superset_slot is required.
`distance_meters`	No	Corrected session distance in meters. Server converts it; do not convert it yourself.
`remove_exercises`	No	Exercises to remove; matched sets deleted, empty slots removed automatically. See SUPERSET SLOTS above.
`rename_exercises`	No	Rename logged exercises in place.
`saved_workout_id`	No	Saved Workout ID to update instead of a completed workout session.
`heart_points_peak`	No	New peak heart points.
`input_distance_unit`	No	Set to km when the user gave km for the _mi fields in this object. Omit when they are already mi.
`saved_workout_title`	No	Optional new title for the Saved Workout.
`heart_points_moderate`	No	New moderate heart points.
`saved_exercise_updates`	No	Optional prescription edits matched first by exact Saved Workout exercise name, then by a unique canonical library match.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Human-readable result text returned by the tool.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 26, 2026
- addedInput schema / properties / calories / maximum
```
Added value: +10000
```
- addedInput schema / properties / distance_km / maximum
```
Added value: +804.672
```
- addedInput schema / properties / distance_meters / maximum
```
Added value: +804672.0000000001
```
- addedInput schema / properties / distance_mi / maximum
```
Added value: +500
```
- addedInput schema / properties / duration_sec / maximum
```
Added value: +86400
```

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / add_exercises / description

Previous value: -"New exercises to add. Call list_exercises first for canonical names."New value: +"New exercises to add. Reuse known canonical names; list_exercises if unknown."

Changed2 schema fields changedSep 18, 2026

changedInput schema / properties / saved_exercise_updates / description

Previous value: -"Optional prescription edits matched by exercise name inside the Saved Workout."New value: +"Optional prescription edits matched first by exact Saved Workout exercise name, then by a unique canonical library match."

changedInput schema / properties / saved_exercise_updates / items / properties / name / description

Previous value: -"Exercise name in the Saved Workout. Required."New value: +"Exercise name. Exact Saved Workout name preferred; a unique canonical library name is also accepted. Required."

Changed5 schema fields changedSep 13, 2026

changedInput schema / properties / add_exercises / items / properties / sets / items / properties / is_bodyweight / description

Previous value: -"True if no external weight."New value: +"True only when genuinely bodyweight. Omit when external load is unknown."

changedInput schema / properties / add_exercises / items / properties / sets / items / properties / weight_lb / description

Previous value: -"Load. Omit for bodyweight. In lb, or kg with input_weight_unit set. See UNIT INPUTS."New value: +"Load. Omit when unknown or bodyweight; never invent it. In lb, or kg with input_weight_unit set. See UNIT INPUTS."

addedInput schema / properties / set_updates / items / properties / clear_weight

Added value: +{
+  "description": "True to clear a wrong stored external load while keeping this set non-bodyweight. Use is_bodyweight=true instead when the corrected set was bodyweight.",
+  "type": "boolean"
+}

addedInput schema / properties / set_updates / items / properties / is_bodyweight

Added value: +{
+  "description": "True to correct this set to bodyweight; clears stored external load/band state. False marks it non-bodyweight without inventing a load.",
+  "type": "boolean"
+}

changedInput schema / properties / set_updates / items / properties / weight_lb / description

Previous value: -"Corrected load. In lb, or kg with input_weight_unit set. See UNIT INPUTS."New value: +"Corrected external load. If the stored load is wrong and the real load is unknown, use clear_weight=true instead of inventing a number. In lb, or kg with input_weight_unit set. See UNIT INPUTS."

Changed11 schema fields changedSep 12, 2026

addedInput schema / properties / add_sets

Added value: +{
+  "description": "Add one or more sets to an exercise already present in this workout. Use add_exercises only for a brand-new exercise.",
+  "items": {
+    "properties": {
+      "exercise_name": {
+        "description": "Exact existing exercise name from get_workout.",
+        "type": "string"
+      },
+      "sets": {
+        "description": "New sets. Omitted values inherit from the exercise's current last set, so [{}] means add one more matching set.",
+        "items": {
+          "properties": {
+            "band_label_lb": {
+              "description": "In lb, or kg with input_weight_unit set. See UNIT INPUTS.",
+              "minimum": 0,
+              "type": "number"
+            },
+            "hold_length_sec": {
+              "minimum": 1,
+              "type": "integer"
+            },
+            "input_weight_unit": {
+              "description": "Set to kg when the user gave kg for the _lb fields in this object. Omit when they are already lb.",
+              "enum": [
+                "lb",
+                "kg"
+              ],
+              "type": "string"
+            },
+            "is_band": {
+              "type": "boolean"
+            },
+            "is_bodyweight": {
+              "type": "boolean"
+            },
+            "notes": {
+              "type": "string"
+            },
+            "reps": {
+              "minimum": 1,
+              "type": "integer"
+            },
+            "rpe": {
+              "maximum": 10,
+              "minimum": 1,
+              "type": "number"
+            },
+            "weight_lb": {
+              "description": "In lb, or kg with input_weight_unit set. See UNIT INPUTS.",
+              "minimum": 0,
+              "type": "number"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "superset_slot": {
+        "description": "Required only when this exercise name appears in more than one slot.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "exercise_name",
+      "sets"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / calories

Added value: +{
+  "description": "Corrected session calories when known.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / distance_km

Added value: +{
+  "description": "Corrected session distance in kilometers. Server converts it; do not convert it yourself.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / distance_meters

Added value: +{
+  "description": "Corrected session distance in meters. Server converts it; do not convert it yourself.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / distance_mi

Added value: +{
+  "description": "Corrected session distance in miles. Use only when the user gave miles. In mi, or km with input_distance_unit set. See UNIT INPUTS.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / duration_sec

Added value: +{
+  "description": "Corrected total session duration in seconds.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / input_distance_unit

Added value: +{
+  "description": "Set to km when the user gave km for the _mi fields in this object. Omit when they are already mi.",
+  "enum": [
+    "mi",
+    "km"
+  ],
+  "type": "string"
+}

changedInput schema / properties / move_exercises / description

Previous value: -"Move exercises between superset slots."New value: +"Move exercises between superset slots. When the same exercise name appears in multiple slots, from_superset_slot is required."

addedInput schema / properties / move_exercises / items / properties / from_superset_slot

Added value: +{
+  "description": "Source slot from get_workout. Required when the exercise name appears in multiple slots.",
+  "type": "string"
+}

changedInput schema / properties / session_id / description

Previous value: -"Session ID, if known. See FIND THE SESSION above."New value: +"Positive session ID returned by a workout tool. If unknown, omit and use session_date + name; never guess."

addedInput schema / properties / session_id / minimum
```
Added value: +1
```

Changed6 schema fields changedSep 12, 2026
- addedInput schema / properties / add_exercises / items / properties / sets / items / properties / rpe / maximum
```
Added value: +10
```
- addedInput schema / properties / add_exercises / items / properties / sets / items / properties / rpe / minimum
```
Added value: +1
```
- addedInput schema / properties / rpe / maximum
```
Added value: +10
```
- addedInput schema / properties / rpe / minimum
```
Added value: +1
```
- addedInput schema / properties / set_updates / items / properties / rpe / maximum
```
Added value: +10
```
- addedInput schema / properties / set_updates / items / properties / rpe / minimum
```
Added value: +1
```

Changed51 schema fields changedSep 7, 2026

changedInput schema / properties / add_exercises / description

Previous value: -"New exercises to add to this session. Call list_exercises first to get canonical names. Optional."New value: +"New exercises to add. Call list_exercises first for canonical names."

changedInput schema / properties / add_exercises / items / properties / name / description

Previous value: -"Exercise name — use canonical name from list_exercises. Required."New value: +"Canonical name from list_exercises."

changedInput schema / properties / add_exercises / items / properties / sets / description

Previous value: -"All sets for this exercise. Required."New value: +"Every set for this exercise."

changedInput schema / properties / add_exercises / items / properties / sets / items / properties / band_label_lb / description

Previous value: -"Band label weight in POUNDS, always. Optional."New value: +"Band label weight; defaults to weight_lb. In lb, or kg with input_weight_unit set. See UNIT INPUTS."

changed

Input schema / properties / add_exercises / items / properties / sets / items / properties / hold_length_sec / description

Previous value: -"Hold/carry duration in seconds. Can coexist with reps and weight_lb. Optional."New value: +"Hold/carry seconds."

addedInput schema / properties / add_exercises / items / properties / sets / items / properties / input_weight_unit

Added value: +{
+  "description": "Set to kg when the user gave kg for the _lb fields in this object. Omit when they are already lb.",
+  "enum": [
+    "lb",
+    "kg"
+  ],
+  "type": "string"
+}

changedInput schema / properties / add_exercises / items / properties / sets / items / properties / is_band / description
```
Previous value: -"True if resistance band. Optional."New value: +"True for a band."
```
changedInput schema / properties / add_exercises / items / properties / sets / items / properties / is_bodyweight / description
```
Previous value: -"True if no external weight. Optional."New value: +"True if no external weight."
```
changedInput schema / properties / add_exercises / items / properties / sets / items / properties / notes / description
```
Previous value: -"Per-set notes. Optional."New value: +"Per-set notes."
```
changedInput schema / properties / add_exercises / items / properties / sets / items / properties / reps / description
```
Previous value: -"Reps this set. Optional."New value: +"Reps this set."
```

changedInput schema / properties / add_exercises / items / properties / sets / items / properties / rpe / description

Previous value: -"Per-set Rate of Perceived Exertion (1-10, half steps like 7.5 allowed, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."New value: +"RPE for this one set, same 1-10 scale as the session rpe field. Only when the user gives per-set effort."

changedInput schema / properties / add_exercises / items / properties / sets / items / properties / weight_lb / description

Previous value: -"Load in POUNDS, always — regardless of the user’s display unit. Convert from kg if needed (kg × 2.2046). Optional."New value: +"Load. Omit for bodyweight. In lb, or kg with input_weight_unit set. See UNIT INPUTS."

changedInput schema / properties / add_exercises / items / properties / slot_type / description

Previous value: -"Slot type for a new slot. Default: working. Ignored if to_superset_slot is set."New value: +"Slot type for a new slot, default working. Ignored with to_superset_slot."

changedInput schema / properties / add_exercises / items / properties / to_superset_slot / description

Previous value: -"Existing slot to join (e.g. \"SS1\"). Omit to create a new standalone slot."New value: +"Existing slot to join, e.g. \"SS1\". Omit for a new standalone slot."

changedInput schema / properties / date / description

Previous value: -"Updated session date. Format: YYYY-MM-DD. Optional."New value: +"New session date, YYYY-MM-DD."

changedInput schema / properties / focus_type / description

Previous value: -"Updated workout category (e.g. Push, Pull, Legs). Optional."New value: +"New category, e.g. Push, Pull, Legs."

changedInput schema / properties / heart_points_moderate / description

Previous value: -"Updated moderate heart points. Optional."New value: +"New moderate heart points."

changedInput schema / properties / heart_points_peak / description

Previous value: -"Updated peak heart points. Optional."New value: +"New peak heart points."

changedInput schema / properties / location / description

Previous value: -"Updated location (e.g. Gym, Home). Optional."New value: +"New location, e.g. Gym, Home."

changedInput schema / properties / move_exercises / description

Previous value: -"Move exercises between superset slots. Optional."New value: +"Move exercises between superset slots."

changedInput schema / properties / move_exercises / items / properties / exercise_name / description

Previous value: -"Exact exercise name from get_workout. Required."New value: +"Exact name from get_workout."

changedInput schema / properties / move_exercises / items / properties / to_superset_slot / description

Previous value: -"Target slot name (e.g. \"SS1\") or \"new\" to make it standalone. Required."New value: +"Target slot, e.g. \"SS1\", or \"new\" for standalone."

addedInput schema / properties / name

Added value: +{
+  "description": "Substring of the focus/type, e.g. \"Push\", case-insensitive, to pick between sessions on session_date. Only without session_id.",
+  "type": "string"
+}

changedInput schema / properties / notes / description

Previous value: -"Updated session notes. Optional."New value: +"New session notes."

changedInput schema / properties / remove_exercises / items / properties / name / description

Previous value: -"Exact exercise name from get_workout. Required."New value: +"Exact name from get_workout."

changedInput schema / properties / remove_sets / description

Previous value: -"Set IDs to delete (get_workout's set_id:N). Remaining sets renumber; emptied exercise/slot removed automatically. Optional."New value: +"Sets to delete. See OPERATIONS above."

addedInput schema / properties / remove_sets / items / properties

Added value: +{
+  "exercise_name": {
+    "description": "Exact name from get_workout, with set_position instead of set_id.",
+    "type": "string"
+  },
+  "set_id": {
+    "description": "set_id:N from get_workout. Alternative to exercise_name + set_position.",
+    "type": "integer"
+  },
+  "set_position": {
+    "description": "1-based set number. Needs exercise_name.",
+    "type": "integer"
+  }
+}

changedInput schema / properties / remove_sets / items / type
```
Previous value: -"integer"New value: +"object"
```

changedInput schema / properties / rename_exercises / description

Previous value: -"Rename logged exercises in place. Preserves set IDs, RPE, notes; recomputes NSI. Optional."New value: +"Rename logged exercises in place."

changedInput schema / properties / rename_exercises / items / properties / from_name / description

Previous value: -"Current exercise name from get_workout (exact match). Required."New value: +"Current name from get_workout, exact."

changedInput schema / properties / rename_exercises / items / properties / to_name / description

Previous value: -"New exercise name. Use the canonical name from list_exercises whenever a match exists. Required."New value: +"New name. Canonical name from list_exercises where one matches."

changedInput schema / properties / rpe / description

Previous value: -"Session-level Rate of Perceived Exertion (1-10, half steps like 7.5 allowed, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — infer from user comments about overall difficulty, or omit."New value: +"Session RPE, 1-10, half steps allowed: 5 moderate, 7 hard, 9 one rep left, 10 failure. Infer from comments about overall difficulty, or omit."

addedInput schema / properties / saved_exercise_updates

Added value: +{
+  "description": "Optional prescription edits matched by exercise name inside the Saved Workout.",
+  "items": {
+    "properties": {
+      "input_weight_unit": {
+        "description": "Set to kg when the user gave kg for the _lb fields in this object. Omit when they are already lb.",
+        "enum": [
+          "lb",
+          "kg"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "description": "Exercise name in the Saved Workout. Required.",
+        "type": "string"
+      },
+      "reps": {
+        "description": "Updated prescribed reps per set. Optional.",
+        "type": "integer"
+      },
+      "sets": {
+        "description": "Updated prescribed set count. Optional.",
+        "type": "integer"
+      },
+      "weight_lb": {
+        "description": "Updated prescribed load in pounds. Optional. In lb, or kg with input_weight_unit set. See UNIT INPUTS.",
+        "type": "number"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / saved_workout_id

Added value: +{
+  "description": "Saved Workout ID to update instead of a completed workout session.",
+  "type": "integer"
+}

addedInput schema / properties / saved_workout_title

Added value: +{
+  "description": "Optional new title for the Saved Workout.",
+  "type": "string"
+}

addedInput schema / properties / session_date

Added value: +{
+  "description": "YYYY-MM-DD, defaults to today. Finds the session when session_id is omitted. Distinct from `date`, which CHANGES the stored date.",
+  "type": "string"
+}

changedInput schema / properties / session_id / description

Previous value: -"Session ID to update. Required."New value: +"Session ID, if known. See FIND THE SESSION above."

changedInput schema / properties / set_updates / description

Previous value: -"Individual set corrections. Optional."New value: +"Individual set corrections."

changedInput schema / properties / set_updates / items / properties / band_label_lb / description

Previous value: -"Band label weight in POUNDS, always. Defaults to weight_lb if omitted. Optional."New value: +"Band label weight; defaults to weight_lb. In lb, or kg with input_weight_unit set. See UNIT INPUTS."

addedInput schema / properties / set_updates / items / properties / exercise_name

Added value: +{
+  "description": "Exact name from get_workout, with set_position instead of set_id.",
+  "type": "string"
+}

changedInput schema / properties / set_updates / items / properties / hold_length_sec / description

Previous value: -"Corrected hold/carry duration in seconds. Can coexist with reps and weight_lb. Optional."New value: +"Corrected hold/carry seconds."

addedInput schema / properties / set_updates / items / properties / input_weight_unit

Added value: +{
+  "description": "Set to kg when the user gave kg for the _lb fields in this object. Omit when they are already lb.",
+  "enum": [
+    "lb",
+    "kg"
+  ],
+  "type": "string"
+}

changedInput schema / properties / set_updates / items / properties / is_band / description
```
Previous value: -"True if resistance band. Optional."New value: +"True for a band."
```
changedInput schema / properties / set_updates / items / properties / reps / description
```
Previous value: -"Corrected rep count. Optional."New value: +"Corrected rep count."
```

changedInput schema / properties / set_updates / items / properties / rpe / description

Previous value: -"Per-set Rate of Perceived Exertion (1-10, half steps like 7.5 allowed, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."New value: +"RPE for this one set, same 1-10 scale as the session rpe field. Only when the user gives per-set effort."

changedInput schema / properties / set_updates / items / properties / set_id / description

Previous value: -"Set ID from get_workout output (shown as set_id:N). Required per entry."New value: +"set_id:N from get_workout. Alternative to exercise_name + set_position."

changedInput schema / properties / set_updates / items / properties / set_notes / description
```
Previous value: -"Updated per-set note. Optional."New value: +"Updated per-set note."
```

addedInput schema / properties / set_updates / items / properties / set_position

Added value: +{
+  "description": "1-based set number, get_workout's \"Set N\". Needs exercise_name.",
+  "type": "integer"
+}

changedInput schema / properties / set_updates / items / properties / weight_lb / description

Previous value: -"Corrected weight in POUNDS, always — regardless of the user’s display unit. Convert from kg if needed (kg × 2.2046). Optional."New value: +"Corrected load. In lb, or kg with input_weight_unit set. See UNIT INPUTS."

removedInput schema / properties / set_updates / items / required
```
Removed value: -[
-  "set_id"
-]
```
removedInput schema / required
```
Removed value: -[
-  "session_id"
-]
```

Changed4 schema fields changedAug 4, 2026

changedInput schema / properties / add_exercises / items / properties / sets / items / properties / band_label_lb / description
```
Previous value: -"Band label weight in pounds. Optional."New value: +"Band label weight in POUNDS, always. Optional."
```

changedInput schema / properties / add_exercises / items / properties / sets / items / properties / weight_lb / description

Previous value: -"Load in pounds. Optional."New value: +"Load in POUNDS, always — regardless of the user’s display unit. Convert from kg if needed (kg × 2.2046). Optional."

changedInput schema / properties / set_updates / items / properties / band_label_lb / description

Previous value: -"Band label weight in pounds. Defaults to weight_lb if omitted. Optional."New value: +"Band label weight in POUNDS, always. Defaults to weight_lb if omitted. Optional."

changedInput schema / properties / set_updates / items / properties / weight_lb / description

Previous value: -"Corrected weight in pounds. Optional."New value: +"Corrected weight in POUNDS, always — regardless of the user’s display unit. Convert from kg if needed (kg × 2.2046). Optional."

Changed6 schema fields changedAug 2, 2026

changedInput schema / properties / add_exercises / items / properties / sets / items / properties / rpe / description

Previous value: -"Per-set Rate of Perceived Exertion (1-10, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."New value: +"Per-set Rate of Perceived Exertion (1-10, half steps like 7.5 allowed, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."

changedInput schema / properties / add_exercises / items / properties / sets / items / properties / rpe / type
```
Previous value: -"integer"New value: +"number"
```

changedInput schema / properties / rpe / description

Previous value: -"Session-level Rate of Perceived Exertion (1-10, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — infer from user comments about overall difficulty, or omit."New value: +"Session-level Rate of Perceived Exertion (1-10, half steps like 7.5 allowed, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — infer from user comments about overall difficulty, or omit."

changedInput schema / properties / rpe / type

Previous value: -"integer"New value: +"number"

changedInput schema / properties / set_updates / items / properties / rpe / description

Previous value: -"Per-set Rate of Perceived Exertion (1-10, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."New value: +"Per-set Rate of Perceived Exertion (1-10, half steps like 7.5 allowed, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."

changedInput schema / properties / set_updates / items / properties / rpe / type
```
Previous value: -"integer"New value: +"number"
```

First observedAug 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark this destructive, and the description adds substantial behavioral detail: set renumbering after removal, automatic removal of emptied slots, preservation of set IDs/RPE/notes on rename, no NSI scoring for literal names, server-side unit conversion, and errors with "nothing changed" on ambiguous matches. None of this contradicts the annotations, and it meaningfully clarifies post-conditions.

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?

The description is densely structured into labeled sections and every sentence carries operational value, which is appropriate for a 26-parameter destructive tool. However, it opens with UNIT INPUTS before stating the tool's purpose, so it is not optimally front-loaded, and some points repeat schema descriptions. The length is largely justified by complexity, but it could be tightened.

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?

The description covers session selection, all five operation groups, superset slot handling, literal naming, equipment semantics, saved workouts, cardio totals, and explicit inference rules for defaults. It also tells the agent when to consult get_workout and list_exercises. Since an output schema exists, the absence of return-value detail is acceptable; nothing needed to call this tool correctly is missing.

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 100%, so the baseline is 3, but the description adds crucial operational semantics beyond the schema: unit conversion rules, the clear_weight versus is_bodyweight decision, set_id versus exercise_name+set_position addressing, superset_slot disambiguation, and the laterality caveat for equipment. These details materially change how parameters should be populated and prevent silent errors like halved NSI scores.

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?

The description states a specific verb and resource — "Update a workout session" — and enumerates the exact operation families: correct metadata, fix set values, rename/add/remove exercises or sets, and move exercises between supersets. This clearly distinguishes it from siblings like log_workout, get_workout, and delete_workout. Even though UNIT INPUTS appears first, the core purpose is explicit and unambiguous.

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?

The description gives thorough routing guidance: call directly with session_id or session_date+name, use get_workout only for detail, and use list_exercises only for unknown canonical names. It also draws explicit lines between add_sets and add_exercises, completed workouts versus saved_workout_id, and when to ask the user versus when to infer. Exclusions such as "never guess" session ids and ambiguity errors are clearly stated.

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

All Wellness Project tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

update_workout

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources