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

smartgym_update_routine

DestructiveIdempotent

Edit a SmartGym routine’s name, weekdays, goal, or note by passing only the fields to change; use dry-run validation before syncing edits to the server.

Instructions

Edit a routine's name, days, goal or note (only the fields you pass; "" or, for days, [] clears).

The goal can be changed but not cleared (the app can't save a routine without one).
A new name must not match another active routine. dry_run=false snapshots the
routine, sends the edit, and verifies it on the server.

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

Input Schema

NameRequiredDescriptionDefault
daysNoWeekdays, 1 = Sunday, 2 = Monday … 7 = Saturday (e.g. [2, 4, 6]); [] clears
goalNo
nameNo
noteNo
dry_runNo
routineYes

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 / properties / days / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "enum": [
      +        1,
      +        2,
      +        3,
      +        4,
      +        5,
      +        6,
      +        7
      +      ],
      +      "type": "integer"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / days / description
      Previous value: -"Days: comma-separated weekday numbers, 1 = Sunday, 2 = Monday … 7 = Saturday (e.g. \"2,4,6\"); \"\" clears"New value: +"Weekdays, 1 = Sunday, 2 = Monday … 7 = Saturday (e.g. [2, 4, 6]); [] clears"
    • changedInput schema / properties / goal / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "Free text, e.g. \"Strength\"; must not be blank",
      +    "type": "string"
      +  },
      +  {
      +    "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=true and openWorldHint=true, and the description adds genuinely useful context: partial-update semantics, clearing rules, the name-uniqueness constraint, and that dry_run=false snapshots then verifies server-side. That is solid value, though it never spells out that the default dry_run=true means nothing is written, which is the single most important behavioral fact for this tool.

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?

Three short, front-loaded sentences with no filler; the partial-update rule comes first, then constraints, then the dry-run behavior. Stray line breaks and escaped quotes make it slightly rougher than it needs to be but nothing is wasted.

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 the mutation risk is reasonably covered. However, for a 6-parameter destructive tool with 17% schema coverage, leaving the required 'routine' identifier and the dry_run default unexplained is a meaningful gap.

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 coverage is only 17%, so the description has to compensate and does so only partially: it covers clearing semantics for name/days/goal/note and the goal constraint. The required 'routine' parameter is never explained (ID vs. name), and the dry_run default is left implicit.

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?

Names a specific verb and resource ("Edit a routine") plus the exact editable fields (name, days, goal, note), so the scope is unambiguous. It does not explicitly differentiate from siblings such as smartgym_get_routine or smartgym_reorder_routine, which keeps it from 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 Guidelines4/5

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

States clearly when behavior applies: only the fields you pass are edited, "" or [] clears, and a goal can be changed but not cleared because the app cannot save a routine without one. Those are real preconditions and exclusions, though it gives no guidance on when to prefer a sibling tool over this one.

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