Skip to main content
Glama
smart-gym-mcp
by sla1k

smartgym_add_exercise

Destructive

Add a built-in or custom exercise to a routine's warmup, main, or cooldown section, with optional position, rest, note, and template sets.

Instructions

Add a catalog exercise (built-in or custom) to a routine section (warmup / main / cooldown).

`position` counts within the section (0 = first; omitted = last). Optional rest,
note and template sets.

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": {
      "routine": "<routine>",
      "exercise": "<exercise>"
    },
    "name": "smartgym_add_exercise"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
setsNo
dry_runNo
routineYes
sectionNomain
exerciseYes
positionNo
rest_secondsNo

Output Schema

NameRequiredDescriptionDefault
noticeYes
changesYes
dry_runYes
routineYes
requestsYes
snapshotYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.1.0
    • changedInput schema / $defs / SetSpec / properties / reps / description
      Previous value: -"Target reps for this set"New value: +"Target reps for this set; for a timed exercise (e.g. Plank, Dead Hang) the duration in seconds"
    • changedInput schema / properties / rest_seconds / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "Rest between sets, in seconds",
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sets / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "$ref": "#/$defs/SetSpec"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "Template sets [{reps, weight_kg}], in order",
      +    "items": {
      +      "$ref": "#/$defs/SetSpec"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / $defs / AddedInOrder
      Added value: +{
      +  "description": "An added exercise's place in `ChangeSet.final_order`: `ChangeSet.added[index]`.",
      +  "properties": {
      +    "index": {
      +      "title": "Index",
      +      "type": "integer"
      +    },
      +    "kind": {
      +      "const": "added",
      +      "default": "added",
      +      "title": "Kind",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "index"
      +  ],
      +  "title": "AddedInOrder",
      +  "type": "object"
      +}
    • changedOutput schema / $defs / ChangeSet / properties / final_order / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "discriminator": {
      +        "mapping": {
      +          "added": "#/$defs/AddedInOrder",
      +          "kept": "#/$defs/KeptInOrder"
      +        },
      +        "propertyName": "kind"
      +      },
      +      "oneOf": [
      +        {
      +          "$ref": "#/$defs/KeptInOrder"
      +        },
      +        {
      +          "$ref": "#/$defs/AddedInOrder"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / $defs / ChangeSet / properties / order
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "title": "Order",
      -  "type": "array"
      -}
    • removedOutput schema / $defs / ChangeSet / properties / routine_identifier
      Removed value: -{
      -  "title": "Routine Identifier",
      -  "type": "integer"
      -}
    • removedOutput schema / $defs / ChangeSet / properties / routine_name
      Removed value: -{
      -  "title": "Routine Name",
      -  "type": "string"
      -}
    • changedOutput schema / $defs / ChangeSet / required
      Previous value: -[
      -  "routine_identifier",
      -  "routine_name",
      -  "routine_changes",
      -  "added",
      -  "removed",
      -  "updated",
      -  "order",
      -  "final_order",
      -  "warnings",
      -  "expected"
      -]New value: +[
      +  "routine_changes",
      +  "added",
      +  "removed",
      +  "updated",
      +  "final_order",
      +  "warnings",
      +  "expected"
      +]
    • addedOutput schema / $defs / KeptInOrder
      Added value: +{
      +  "description": "A kept exercise's place in `ChangeSet.final_order`.",
      +  "properties": {
      +    "exercise_id": {
      +      "title": "Exercise Id",
      +      "type": "integer"
      +    },
      +    "kind": {
      +      "const": "kept",
      +      "default": "kept",
      +      "title": "Kind",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "exercise_id"
      +  ],
      +  "title": "KeptInOrder",
      +  "type": "object"
      +}
    • changedOutput schema / $defs / SetSpec / properties / reps / description
      Previous value: -"Target reps for this set"New value: +"Target reps for this set; for a timed exercise (e.g. Plank, Dead Hang) the duration in seconds"
  2. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful positional semantics (0 = first, omitted = last) but omits the most consequential behavior: that dry_run defaults to true, meaning a call may not actually mutate the routine unless explicitly overridden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core action, with the positional rule in a compact parenthetical. No filler or repetition of the tool name.

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?

An output schema exists, so return values need not be described, and the section/position semantics are covered. The main gap is the undisclosed dry_run default on a destructive mutation tool, which an agent needs before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported at 0%, so the description carries real weight; it explains position indexing and the section enum values, and names rest, note and template sets. However, it says nothing about dry_run, routine, or exercise, leaving several of the eight parameters without added meaning.

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 and resource ('Add a catalog exercise ... to a routine section') and scopes it to built-in or custom catalog exercises. The add verb naturally separates it from the sibling move/remove/update exercise tools without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not guidance, and no mention of the alternatives (smartgym_update_exercise, smartgym_move_exercise) that an agent might confuse with this one. It also never says when a dry run is appropriate, despite dry_run defaulting to true.

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