Skip to main content
Glama

update_workout_section_template

Rename a saved workout section or replace its exercises (exercises, when given, replaces the whole list). (confirm-gated: previews until confirm: true)

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": {
      "id": "<id>"
    },
    "name": "update_workout_section_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
sectionNoWhich part of a workout this block fills; applied to every exercise in it
exercisesNo[{ name, sets, reps, restSeconds?, exerciseId?, notes?, modality?, supersetGroup?, ... }] — same shape as create_workout_plan exercises; reps can be a range like "8-12".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses two behaviors the agent cannot see elsewhere: the confirm gate ('previews until confirm: true') and that passing exercises replaces the whole list rather than merging. That replacement warning is the kind of over-write risk an agent needs, though the return shape of the preview versus the applied result is still unstated.

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 sentences, both front-loaded: the operation first, then the confirm-gate caveat. No filler or restatement of the title, and the parentheticals are compact rather than redundant.

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?

For a confirm-gated mutation with no output schema, the description covers the essential risk profile: it previews by default and exercises overwrites the full list. It leaves open how omitted fields (name, section) behave and what the preview returns, but those are secondary for correct invocation given the schema's parameter documentation.

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?

Schema coverage is 60%, so the schema already documents confirm, section, and the exercise object shape. The description adds genuine meaning on top of that by stating that exercises replaces the entire list, which the schema does not say, and by framing 'name' as a rename. The section enum's role is only covered in the schema, not the description.

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 specific verb+resource ('Rename a saved workout section') and states the second supported operation ('replace its exercises'), so an agent can tell it is the section-template mutation tool rather than the plan-template or create/delete siblings. It stops short of explicitly contrasting with update_workout_plan_template, which also lives in the sibling list.

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?

Use is implied by the two named operations (rename, replace exercises) and by the confirm-gated note, giving an agent a reasonable sense of when to call it. There is no explicit when-not guidance and no pointer to the alternative tools for editing the surrounding plan, so routing between this and update_workout_plan_template is left to inference.

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.