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

smartgym_remove_exercise

Destructive

Remove an exercise from a SmartGym routine while preserving logged workout history; use dry-run mode to preview the change before applying it.

Instructions

Remove an exercise from its routine (logged history is kept).

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>"
    },
    "name": "smartgym_remove_exercise"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
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

B3.3/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 risk profile is covered. The description contributes one genuinely useful fact beyond them: logged history is preserved when the exercise is removed. It stops short of describing reversibility, permission requirements, or what happens to exercise ordering in the routine.

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?

A single compact sentence with the action front-loaded and the parenthetical state guarantee placed after it. Nothing is wasted, though the brevity is part of why parameter and usage guidance is missing.

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 need not be explained, and annotations carry the destructiveness signal. Still, for a destructive mutation with a dry_run default of true, the description should say that the default is a no-op preview and confirm whether the removal can be undone. It is adequate but leaves real gaps for correct invocation.

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?

Behaviour is fine, but scoring is 2 because schema coverage is 0% and the description says nothing about the two parameters. The surprising element is dry_run, which defaults to true -- meaning the default call may not actually remove anything -- and the description never explains this toggle or its default. exercise_id is self-evident from its name, but dry_run needs narrative support that is absent.

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?

The description names a concrete verb and resource ('remove an exercise') and adds the scope qualifier 'from its routine', which clarifies that the exercise is detached rather than deleted globally. It does not name or contrast with siblings such as smartgym_update_exercise or smartgym_move_exercise, so a 4 rather than a 5.

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?

There is no when-to-use guidance and no mention of alternatives. An agent cannot tell from the description whether editing an exercise entry should instead go through smartgym_update_exercise or whether removal is the right call versus moving it with smartgym_move_exercise. Usage is only inferable from the tool name.

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