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

smartgym_move_exercise

DestructiveIdempotent

Move an exercise to another workout section or reposition it within a section by specifying the target section and an optional position.

Instructions

Move an exercise to another section (or to another position in its section).

`position` counts within the target section (0 = first; omitted = last).

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": {
      "exercise_id": "<exercise_id>",
      "section": "<section>"
    },
    "name": "smartgym_move_exercise"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
sectionYes
positionNo
exercise_idYes

Output Schema

NameRequiredDescriptionDefault
noticeYes
changesYes
dry_runYes
routineYes
requestsYes
snapshotYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.0
    • 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 and idempotentHint=true, so the safety profile is partly covered. The description adds the key positional rule, but omits the significant behavioral fact that dry_run defaults to true (so calls are simulations unless explicitly disabled) and doesn't say whether other exercises' positions shift.

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 with zero waste; the move semantics are front-loaded and the positional rule follows immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 needn't be described, and the positional semantics are covered. But for a destructive tool with an undocumented dry_run defaulting to true, the description leaves an agent without the most important operational detail.

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

Parameters4/5

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

With 0% schema description coverage, the description carries the burden and does define `position` precisely: it counts within the target section, 0 is first, and omitting it means last. It leaves `dry_run` (whose default true is behaviorally critical) and `exercise_id` unexplained, but the enum on `section` is self-documenting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: moving an exercise to another section or to another position within its section. It clearly delineates its scope, though it never contrasts itself with siblings like smartgym_update_exercise or smartgym_reorder_routine.

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 parenthetical clarifies that the tool handles both cross-section moves and in-section reordering, which implies when to reach for it. However, there is no explicit when-to-use vs. alternatives guidance or stated prerequisites.

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