Skip to main content
Glama

create_workout

Create a user-approved workout template with exercises, sets, loads, rest modes, and optional supersets. Exercise names must be exact display names from the catalog or the user's custom exercises.

Each exercise: name, target (reps|time), load (weight|percent), working_rest_mode (timed|off|lap), working_rest_seconds (required when working_rest_mode is 'timed'; omit otherwise), optional warmup_sets[], optional warmup_rest_mode (required when warmup_sets is present; same allowed values as working_rest_mode), optional warmup_rest_seconds (required when warmup_rest_mode is 'timed'), working_sets[] (min 1), and an optional superset label. working_rest_mode 'off' means continue straight to the next set/exercise with no rest. 'lap' means the watch pauses until the user presses the lap button. The same rest setting applies between sets within the exercise and after the exercise's last set (the inter-exercise rest). Each set has reps (when target=reps) or seconds (when target=time), and weight (when load=weight) or percent (when load=percent), plus optional rpe. weight is in the user's units (0 = bodyweight). percent is the percentage of training max itself, e.g. 65 for 65%, not a computed weight. The server computes the weight from the user's training max, and the call fails with a clear error if the exercise has no training max set. superset is an optional short label (case-insensitive, max 16 chars). Exercises sharing a label run as one superset on the watch — at least two exercises must share a label, max 16 distinct labels per workout. Optional folder_name is an exact folder name; it places the workout in that folder, or creates the folder if no folder has that name.

Example with a two-exercise superset: {"name":"Push","exercises":[{"name":"Barbell Bench Press","target":"reps","load":"weight","working_rest_mode":"timed","working_rest_seconds":90,"working_sets":[{"reps":5,"weight":185}],"superset":"A"},{"name":"Cable Row","target":"reps","load":"weight","working_rest_mode":"lap","working_sets":[{"reps":8,"weight":80}],"superset":"A"}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
exercisesYesExercises in workout order. 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.
folder_nameNoOptional exact folder name to place the workout in. The folder is created if no folder has this name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
set_countYes
folder_nameNo
exercise_countYes
folder_createdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / exercises / description
      Added value: +"Exercises in workout order. 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
  2. Changed3 schema fields changed
    • 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."
    • changedInput schema / properties / folder_name / description
      Previous value: -"Optional folder to place the workout in. The folder is created if no folder has this name. Call get_folders to see existing folders."New value: +"Optional exact folder name to place the workout in. The folder is created if no folder has this name."
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only indicate readOnlyHint=false and destructiveHint=false, so they carry minimal behavioral info. The description extensively discloses behavior: rest mode semantics ('off' continues straight, 'lap' waits for button), percent is a percentage of training max (not computed weight), server computes weight from training max, superset grouping behavior, folder creation if not exists, and step counting rules. This goes well beyond annotations.

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 lengthy but well-organized: it starts with the core purpose, then details each exercise component, rest modes, superset rules, folder handling, and ends with a concrete example. Every sentence adds value, though some redundancy exists (e.g., repeating rest mode definitions in the schema and description). Given the tool's complexity, the length is justified and the structure is clear.

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?

The description covers nearly all operational aspects: exercise structure, rest mode semantics, superset grouping, folder creation, training max dependency, and step counting. It also provides a worked example. With an output schema present, return values need not be explained. Minor gaps: it doesn't mention error cases beyond the training max issue, and the phrase 'user-approved' is not elaborated, but these are negligible for a creation tool.

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 description coverage is 67%, so some parameters lack descriptions. The description fills these gaps by explaining 'weight is in the user's units (0 = bodyweight)', 'percent is the percentage of training max itself, e.g. 65 for 65%', the meaning of 'off' and 'lap' rest modes, and the constraint that working_rest_seconds is required when mode is 'timed' and omitted otherwise. It also clarifies superset label constraints and the step counting rule.

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 opens with a specific verb+resource: 'Create a user-approved workout template with exercises, sets, loads, rest modes, and optional supersets.' It clearly distinguishes from sibling tools like update_workout and delete_workout by focusing on creation, and it names the exact input domains (exercise names, sets, loads, rest modes, supersets).

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 description states prerequisites like 'Exercise names must be exact display names from the catalog or the user's custom exercises' and explains conditions like 'fails with a clear error if the exercise has no training max set.' However, it does not explicitly compare to update_workout or mention when to use this tool versus siblings, leaving usage context implicit rather than explicit.

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