Wellness Project

log_workout

Destructive

UNIT INPUTS: never convert units yourself. For each canonical field below, pass the user's number exactly as stated when it is already in the canonical unit; when they gave the alternate unit instead, pass the same number unconverted and set the matching companion field so the tool converts once before storage. Omit the companion when the number is already canonical. This overrides any wording that asks you to do the arithmetic.

_lb fields: lb, or kg with input_weight_unit set.
_mi fields: mi, or km with input_distance_unit set.
_in fields: in, or cm with input_length_unit set.
_stated_g fields: g, or oz with input_mass_unit set.
_stated_ml fields: ml, or fl_oz with input_volume_unit set.

Log a complete workout session: exercises, sets, reps, weights, and session metadata. Use when the user describes finishing a workout, lists exercises performed, or asks to log training. A workout they have not done yet is not a log: use propose_workout for that.

EXERCISE NAMES:

Call list_exercises first; match each exercise to the closest canonical name. No reasonable match → use the name as stated. Don't ask before logging, match silently and log.
"Chest press" (machine) and "bench press" (barbell) are DISTINCT — pass the user's term through so the resolver's aliases pin the right one.
name is ONLY the exercise name, never reps/weights/sets — those go in the sets array.
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.
The result says when a name was matched to something other than what the user said. Relay it in your own words rather than repeating the line verbatim. 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.
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.

SETS:

"3 sets of 15 reps" → 3 set objects with reps: 15. "15/12/10" → 3 sets with reps 15, 12, 10.
Pure isometric holds (planks, dead hangs, wall sits) have no reps: "30 second plank" = { hold_length_sec: 30 }.
Tempo/pause work combines reps + weight_lb + hold_length_sec (seconds per rep) on the same set, never in notes.
Loaded carries (farmers carry, sled push, weighted plank) are one set per trip: hold_length_sec + weight_lb, omit reps unless a trip count is given. weight_lb is PER HAND for a two-implement carry, TOTAL for one implement. Distance has no column and is never a duration — put it in notes.

INFER — do not ask:

date: today, or from context
focus_type: from the exercises (bench/shoulders/triceps=Push, rows/pulldowns/curls=Pull, squats/deadlifts/lunges=Legs, mixed upper=Upper, everything=Full Body)
is_bodyweight: true for pull-ups, push-ups, dips, bodyweight squats; missing load alone does not mean bodyweight
superset_group: same integer for exercises done back-to-back or as a superset
slot_type: 'warmup' for prep at the start, 'finisher' for burnout/cardio at the end, 'working' (default) otherwise

RPE (Rate of Perceived Exertion) — 1-10 scale, half steps allowed (7.5, 8.5):

Session-level RPE: overall session difficulty. Infer from user comments like "brutal session" (8-9) or "easy day" (3-4). Optional.
Per-set RPE: how hard each individual set felt. Include only if the user explicitly mentions per-set effort or failure. Optional.
Scale: 1=minimal effort, 5=moderate, 7=hard, 8=few reps left, 9=one rep left, 10=maximal/failure.

ASK (single batched question) only if missing and not inferable: location, focus_type (list ambiguous), heart_points (tracker provides them but not mentioned).

RETURNS the new session's ID (as "[ID NN]"). Pass it to update_workout / delete_workout / get_workout / add_exercises for follow-ups in this conversation.

LIVE LOADS: for user-driven completed-workout logging, obvious bodyweight movements may omit load and are inferred as bodyweight. If a performed set normally uses external resistance, include that set's load. If the user did not provide it, ask one batched clarification before calling this tool. Only set load_unknown=true on a missing set when the user explicitly says they do not know, do not remember, or want to save without that load. Preserve partial known loads positionally; never copy one set's load to another or treat a missing external load as bodyweight.

SAVED WORKOUT MODE: when the user asks to save a workout for reuse, set save_as_saved_workout=true and pass the full prescription through this same tool. In saved mode the workout is NOT logged as completed history, and LIVE LOADS does not apply: prescribed weight may be omitted. To replace an existing Saved Workout, also pass saved_workout_id; the supplied prescription fully replaces its prior prescribed sets/reps/weights. Use saved_workout_title when the reusable name should differ from focus_type.

SIMPLE CARDIO / ENDURANCE LOGS:

Cycling, biking, bike rides, walking, and rowing/RowErg sessions are workouts, not runs. NEVER use log_run for them.
Log cycling/biking with focus_type: "Cycling", walking with "Walking", and rowing/RowErg with "Rowing".
A simple cardio workout does not need fake strength exercises. Omit exercises (or pass []) and put distance in the unit the user actually supplied: distance_mi, distance_km, or distance_meters. Put elapsed workout time in duration_sec and calories in calories when supplied.
NEVER do distance-unit arithmetic yourself. The server converts km/meters to stored miles exactly.
Do not call list_exercises just to represent a bike ride, walk, or rowing erg. The server stores these directly as workout_sessions.

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`	Yes	YYYY-MM-DD. Default to today.
`notes`	No	Session notes: how it went, PRs hit, how they felt.
`calories`	No	Session calories for simple cardio when supplied by the user/device.
`location`	No	Gym, Home, Outdoor. Infer from context or ask.
`exercises`	No	Every exercise performed, in order.
`focus_type`	No	Infer from the exercises: Push, Pull, Legs, Upper, Lower, Full Body, Cardio, Mobility. Ask only if genuinely unclear.
`distance_km`	No	Session distance in kilometers. Server converts it to storage units; do not convert it yourself.
`distance_mi`	No	Session distance in miles for simple cardio. Use only when the user supplied miles. In mi, or km with input_distance_unit set. See UNIT INPUTS.
`duration_sec`	No	Total session duration in seconds for simple cardio when known.
`distance_meters`	No	Session distance in meters. Server converts it to storage units; do not convert it yourself.
`saved_workout_id`	No	Existing Saved Workout ID to replace in saved mode. Omit to create a new Saved Workout.
`heart_points_peak`	No	Peak-intensity heart points, if mentioned.
`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 reusable workout name in saved mode. Defaults to focus_type.
`heart_points_moderate`	No	Moderate-intensity heart points, Google Fit or equivalent, if mentioned.
`save_as_saved_workout`	No	True when this payload is a reusable Saved Workout prescription, not a completed workout. Defaults to false.

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.

Changed3 schema fields changedSep 13, 2026

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

Previous value: -"True if no external weight. Infer for pull-ups, push-ups, dips."New value: +"True only when genuinely bodyweight. Omit when external load is unknown; existing equipment inference handles obvious bodyweight movements."

addedInput schema / properties / exercises / items / properties / sets / items / properties / load_unknown

Added value: +{
+  "description": "True only when the user explicitly says this set load is unknown, not remembered, or should be saved without it. Never infer this or use it to replace a known load.",
+  "type": "boolean"
+}

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

Previous value: -"Load. For a band, the band label weight (e.g. 80 for an 80lb band). Omit for bodyweight. In lb, or kg with input_weight_unit set. See UNIT INPUTS."New value: +"Load. For a band, the band label weight (e.g. 80 for an 80lb band). Omit when unknown or bodyweight; never invent it. In lb, or kg with input_weight_unit set. See UNIT INPUTS."

Changed6 schema fields changedSep 12, 2026

addedInput schema / properties / calories

Added value: +{
+  "description": "Session calories for simple cardio when supplied by the user/device.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / distance_km

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

addedInput schema / properties / distance_meters

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

changedInput schema / properties / distance_mi / description

Previous value: -"Session distance in miles for simple cardio such as running, cycling/biking, or walking. Do not use for per-exercise loaded-carry distance. In mi, or km with input_distance_unit set. See UNIT INPUTS."New value: +"Session distance in miles for simple cardio. Use only when the user supplied miles. In mi, or km with input_distance_unit set. See UNIT INPUTS."

addedInput schema / properties / distance_mi / minimum
```
Added value: +0
```
addedInput schema / properties / duration_sec / minimum
```
Added value: +1
```

Changed4 schema fields changedSep 12, 2026
- addedInput schema / properties / exercises / items / properties / sets / items / properties / rpe / maximum
```
Added value: +10
```
- addedInput schema / properties / 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
```

Changed4 schema fields changedSep 10, 2026

addedInput schema / properties / distance_mi

Added value: +{
+  "description": "Session distance in miles for simple cardio such as running, cycling/biking, or walking. Do not use for per-exercise loaded-carry distance. In mi, or km with input_distance_unit set. See UNIT INPUTS.",
+  "type": "number"
+}

addedInput schema / properties / duration_sec

Added value: +{
+  "description": "Total session duration in seconds for simple cardio when known.",
+  "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 / required

Previous value: -[
-  "date",
-  "exercises"
-]New value: +[
+  "date"
+]

Changed24 schema fields changedSep 7, 2026

changedInput schema / properties / date / description

Previous value: -"Date of the workout. Format: YYYY-MM-DD. Required — default to today."New value: +"YYYY-MM-DD. Default to today."

changedInput schema / properties / exercises / description

Previous value: -"Ordered list of all exercises performed. Required."New value: +"Every exercise performed, in order."

changedInput schema / properties / exercises / items / properties / name / description

Previous value: -"Exercise name. Required — use the canonical name from list_exercises if a match exists; otherwise use the name as stated."New value: +"Canonical name from list_exercises if one matches, else the name as stated."

changedInput schema / properties / exercises / items / properties / sets / description

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

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

Previous value: -"Band label weight in POUNDS, always (e.g. 80 for an 80lb band). Use when is_band is true. If omitted, weight_lb is used as the band label."New value: +"Band label weight (e.g. 80 for an 80lb band). Use when is_band is true; defaults to weight_lb. In lb, or kg with input_weight_unit set. See UNIT INPUTS."

changedInput schema / properties / exercises / items / properties / sets / items / properties / hold_length_sec / description

Previous value: -"Hold/carry duration in seconds — a timed hold (plank, wall sit, dead hang), seconds-per-rep for deliberate tempo/eccentric work, or trip/round duration for loaded carries (farmers carry, sled push). Can coexist with reps and weight_lb: a loaded carry stores hold_length_sec + weight_lb together, a tempo set stores reps + weight_lb + hold_length_sec."New value: +"Seconds: a timed hold, seconds-per-rep for tempo work, or one carry trip. See SETS above."

addedInput schema / properties / 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 / exercises / items / properties / sets / items / properties / is_band / description

Previous value: -"True if resistance comes from a band (not cable or free weight). Important for NSI scoring — band weight is converted using a movement-specific factor. Infer from context: \"band face pull\", \"80lb band\", etc."New value: +"True for a band, not a cable or free weight; NSI scores band load differently. Infer from \"band face pull\", \"80lb band\"."

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

Previous value: -"True if no external weight was used. Optional — infer true for pull-ups, push-ups, dips, etc."New value: +"True if no external weight. Infer for pull-ups, push-ups, dips."

changedInput schema / properties / exercises / items / properties / sets / items / properties / notes / description

Previous value: -"Per-set notes. Optional — e.g. \"failed last rep\", \"paused at bottom\", carry distance (e.g. \"50 ft\")."New value: +"Per-set notes, e.g. \"failed last rep\", \"paused at bottom\", carry distance \"50 ft\"."

changedInput schema / properties / exercises / items / properties / sets / items / properties / reps / description

Previous value: -"Reps completed this set. Optional — include if stated; omit for a pure hold with no rep count. Can coexist with hold_length_sec (tempo/pause work) and weight_lb."New value: +"Reps this set. Omit for a pure hold. Can coexist with hold_length_sec and weight_lb."

changedInput schema / properties / 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 / 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). For band exercises, this is the band label weight (e.g. 80 for an 80lb band). Optional — omit for bodyweight exercises."New value: +"Load. For a band, the band label weight (e.g. 80 for an 80lb band). Omit for bodyweight. In lb, or kg with input_weight_unit set. See UNIT INPUTS."

changedInput schema / properties / exercises / items / properties / slot_type / description

Previous value: -"Optional. Tag this exercise as warmup, working (default), or finisher. Infer from context: warmup for activation/mobility/light prep at start, finisher for burnout/holds/cardio at end."New value: +"warmup for prep at the start, finisher for burnout/cardio at the end, working otherwise."

changedInput schema / properties / exercises / items / properties / superset_group / description

Previous value: -"Optional. Assign the same positive integer to exercises performed back-to-back as a superset (e.g. both get superset_group: 1). Omit or null for standalone exercises."New value: +"Same positive integer for exercises done back-to-back as a superset. Omit for standalone."

changedInput schema / properties / focus_type / description

Previous value: -"Workout category. Optional — infer from exercises (e.g. Push, Pull, Legs, Upper, Lower, Full Body, Cardio, Mobility). Ask if genuinely unclear."New value: +"Infer from the exercises: Push, Pull, Legs, Upper, Lower, Full Body, Cardio, Mobility. Ask only if genuinely unclear."

changedInput schema / properties / heart_points_moderate / description

Previous value: -"Moderate-intensity heart points earned (Google Fit or equivalent). Optional — include if the user mentions them."New value: +"Moderate-intensity heart points, Google Fit or equivalent, if mentioned."

changedInput schema / properties / heart_points_peak / description

Previous value: -"Peak-intensity heart points earned. Optional — include if mentioned."New value: +"Peak-intensity heart points, if mentioned."

changedInput schema / properties / location / description

Previous value: -"Where the workout took place. Optional — e.g. Gym, Home, Outdoor. Infer from context or ask."New value: +"Gym, Home, Outdoor. Infer from context or ask."

changedInput schema / properties / notes / description

Previous value: -"Free-text session notes. Optional — include anything the user mentions about how the session went, PRs hit, how they felt, etc."New value: +"Session notes: how it went, PRs hit, how they felt."

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 / save_as_saved_workout

Added value: +{
+  "description": "True when this payload is a reusable Saved Workout prescription, not a completed workout. Defaults to false.",
+  "type": "boolean"
+}

addedInput schema / properties / saved_workout_id

Added value: +{
+  "description": "Existing Saved Workout ID to replace in saved mode. Omit to create a new Saved Workout.",
+  "type": "integer"
+}

addedInput schema / properties / saved_workout_title

Added value: +{
+  "description": "Optional reusable workout name in saved mode. Defaults to focus_type.",
+  "type": "string"
+}

Changed2 schema fields changedAug 4, 2026

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

Previous value: -"Band label weight in pounds (e.g. 80 for an 80lb band). Use when is_band is true. If omitted, weight_lb is used as the band label."New value: +"Band label weight in POUNDS, always (e.g. 80 for an 80lb band). Use when is_band is true. If omitted, weight_lb is used as the band label."

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

Previous value: -"Load in pounds. For band exercises, this is the band label weight (e.g. 80 for an 80lb band). Optional — omit for bodyweight exercises."New value: +"Load in POUNDS, always — regardless of the user’s display unit. Convert from kg if needed (kg × 2.2046). For band exercises, this is the band label weight (e.g. 80 for an 80lb band). Optional — omit for bodyweight exercises."

Changed4 schema fields changedAug 2, 2026

changedInput schema / properties / 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 / 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"

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 only declare destructive/readOnly/idempotent flags; the description adds far more: the single-conversion unit contract, the ID returned as '[ID NN]', saved-mode semantics where the workout is not logged as completed history, LIVE LOADS inference policy, and the NSI score implications of equipment tagging. These are behavioral consequences an agent cannot derive from structured fields.

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-loads the highest-risk rule (unit handling) and uses clear headers, so it is navigable. It is nonetheless very long, and several rules restate the same point across sections (e.g., unit conversion is asserted both at top and per-field), costing tightness without losing meaning.

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?

For a 17-parameter tool with an output schema, the description covers inference defaults, the batched-question policy, saved-workout mode, and cardio fallbacks — leaving no decision an agent must make on its own. Return-value explanation is correctly omitted since an output schema exists.

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?

Although schema coverage is 100%, the schema itself repeatedly defers to the description ('See UNIT INPUTS', 'See EQUIPMENT', 'See SETS'), so the description is the authoritative source for param meaning. It defines load basis per equipment value, per-set vs session RPE, hold_length_sec reuse for tempo/carries, and superset/slot inference defaults.

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+resource ('Log a complete workout session: exercises, sets, reps, weights, and session metadata') and explicitly distinguishes itself from siblings by naming propose_workout for future workouts and log_run for cycling/walking/rowing. An agent can route to it without opening any schema.

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 explicit when-to-use triggers ('user describes finishing a workout, lists exercises performed, or asks to log training'), explicit exclusions ('a workout they have not done yet is not a log: use propose_workout'), and named alternatives for follow-ups (update_workout / delete_workout / get_workout / add_exercises) plus the cardio exception to log_run.

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.

log_workout

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources