Skip to main content
Glama

create_workout

Create a 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_id places the workout in an existing folder; optional new_folder_name creates a folder and places the workout in it. Pass at most one. new_folder_name fails when a folder already has that name, and the error gives that folder's folder_id. Optional warmup (workout) and wait_for_lap_after (per exercise) control the open warmup step at the start and the wait for a lap button press between exercises. Omitting them applies the user's workout settings; pass them only when the user asked for something different in this request. Steps the settings add count toward the 100 step limit; if they push the workout over it, the error says so and passing false to make it fit is allowed. The result reports what was applied.

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"}]}

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": {
      "name": "<name>",
      "exercises": "<exercises>"
    },
    "name": "create_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
warmupNoWhether the workout starts with an open warmup step on the watch. Omit to apply the user's workout settings; pass it only when the user asked for something different in this request. Adds one step.
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, one for the workout warmup and one for each wait for lap after an exercise. Off rests add no steps.
folder_idNoOptional folder_id of an existing folder to place the workout in, as the folder list gives it. Not together with new_folder_name.
new_folder_nameNoOptional name of a new folder to create and place the workout in. Fails if a folder already has this name; pass that folder's folder_id instead.

Output Schema

NameRequiredDescriptionDefault
nameYes
warmupYesThe workout starts with the open warmup step
folder_idNo
set_countYes
workout_idYes
folder_nameNo
exercise_countYes
folder_createdYes
wait_for_lap_countYesExercises followed by a wait for the lap button

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / folder_id
      Added value: +{
      +  "description": "Optional folder_id of an existing folder to place the workout in, as the folder list gives it. Not together with new_folder_name.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • removedInput schema / properties / folder_name
      Removed value: -{
      -  "description": "Optional exact folder name to place the workout in. The folder is created if no folder has this name.",
      -  "maxLength": 80,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • addedInput schema / properties / new_folder_name
      Added value: +{
      +  "description": "Optional name of a new folder to create and place the workout in. Fails if a folder already has this name; pass that folder's folder_id instead.",
      +  "maxLength": 80,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedOutput schema / properties / folder_id
      Added value: +{
      +  "type": "string"
      +}
  2. Changed6 schema fields changed
    • changedInput schema / properties / exercises / description
      Previous 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."New 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, 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": "Whether the workout starts with an open warmup step on the watch. Omit to apply the user's workout settings; pass it only when the user asked for something different in this request. Adds one step.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / wait_for_lap_count
      Added value: +{
      +  "description": "Exercises followed by a wait for the lap button",
      +  "type": "number"
      +}
    • addedOutput schema / properties / warmup
      Added value: +{
      +  "description": "The workout starts with the open warmup step",
      +  "type": "boolean"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "workout_id",
      -  "name",
      -  "exercise_count",
      -  "set_count",
      -  "folder_created"
      -]New value: +[
      +  "workout_id",
      +  "name",
      +  "exercise_count",
      +  "set_count",
      +  "warmup",
      +  "wait_for_lap_count",
      +  "folder_created"
      +]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / workout_id
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "name",
      -  "exercise_count",
      -  "set_count",
      -  "folder_created"
      -]New value: +[
      +  "workout_id",
      +  "name",
      +  "exercise_count",
      +  "set_count",
      +  "folder_created"
      +]
  4. 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
  5. 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."
  6. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes far past the annotations: it explains server-side training-max resolution and the resulting clear error, the 100-step budget and how rest/warmup/lap steps consume it (including that passing false to shrink is allowed), that the call fails on duplicate folder names and returns the existing folder_id, and that the response reports what was applied. It also spells out superset execution semantics (interleaved rounds, min two members, max 16 labels) and 'lap' pausing behavior.

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 purpose, then organized thematically by exercise fields, rest semantics, sets, supersets, folders, settings overrides, and capped with a worked example — easy to scan. It is long, and several sentences restate schema text almost verbatim (percent definition, working_rest_mode enum meanings), which is the main inefficiency, but the length is defensible for a deeply nested create payload.

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 complex nested creation tool with a 100-step limit, this covers every failure mode an agent must avoid (missing training max, rest_seconds presence rules, folder name collision, step overflow) and an output schema exists so return values need not be described. Nothing material for a correct invocation 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?

With 80% schema coverage the baseline is 3, but the description adds real meaning beyond the schema: the equivalence between load mode and required set fields, that percent is of the training max itself (65 = 65%) and the server computes the weight, that weight 0 means bodyweight, that the working rest also governs inter-exercise rest, and the mutual exclusivity of folder_id and new_folder_name. The embedded two-exercise superset JSON example concretely disambiguates the nesting.

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 opening sentence gives a precise verb and resource ('Create a workout template') plus the full scope of what a template contains (exercises, sets, loads, rest modes, supersets). 'Template' implicitly separates it from schedule_workout/update_workout, and the naming constraint on exercises signals the catalog dependency without opening a schema.

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?

Strong conditional guidance for parameters: omit warmup/wait_for_lap_after to inherit user settings and 'pass them only when the user asked for something different', pass at most one of folder_id/new_folder_name, and rest_seconds required/omitted depending on mode. It never routes the agent to an alternative tool (e.g. update_workout for existing workouts, validate_exercise_names or search_exercises to resolve names), so tool-selection guidance is incomplete.

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