Skip to main content
Glama

update_workout_plan

Edit an existing workout plan (confirm-gated). Pass planId plus only the fields to change. exercises, if given, REPLACES the whole exercise list — send the full intended list, not just the changed ones; to change a single slot use swap_workout_exercise instead. Each exercise follows the same shape as create_workout_plan (name, sets, reps, restSeconds?, section?, exerciseId?, notes?, modality?, …). days: optional [MONDAY..SUNDAY].

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": {
      "planId": "<planId>"
    },
    "name": "update_workout_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
titleNo
planIdYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
endDateNo
exercisesNo
startDateNoYYYY-MM-DD
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-open-world, non-destructive mutation; the description adds the crucial nuance that exercises REPLACES the entire list, which materially changes the risk profile of a call. The confirm-gate detail is partly redundant with the confirm parameter's schema description. It does not describe failure behavior or what happens to fields omitted from the update, so it stops short of full disclosure.

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 verb and the confirm gate, then ordered by importance: planId, the partial-update rule, the high-risk exercises semantics, then the exercise shape and days. Dense but every clause carries operational weight; the trailing parenthetical field list with an ellipsis is the only slightly loose element.

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?

There is no output schema, so the description must carry behavioral weight, and it does: it covers addressing, partial updates, the list-replacement hazard, the alternative tool, and the nested exercise shape by reference. For an 8-parameter mutation with only 25% schema coverage, this is sufficient to call the tool correctly.

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 schema coverage at 25% for 8 parameters, the description compensates well: it explains planId's role, the replace-vs-merge semantics of exercises, enumerates the allowed days values (MONDAY..SUNDAY), and points to create_workout_plan for the exercise object's shape. Gaps remain for startDate/endDate and title/description, none of which are explained beyond the schema.

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 ("Edit an existing workout plan") plus the gate ("confirm-gated") and how to address it ("Pass planId"). It is immediately distinguishable from create_workout_plan and from swap_workout_exercise, which is named as the narrow-scope alternative.

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

Usage Guidelines5/5

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

Gives explicit when-to guidance (edit an existing plan), an explicit exclusion with the correct alternative ("to change a single slot use swap_workout_exercise instead"), and a partial-update rule ("only the fields to change"). An agent can route correctly without consulting siblings.

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.