Skip to main content
Glama

update_workout_plan_template

Edit an existing workout plan template (confirm-gated). Only send the fields that change.

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_plan_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
goalNo
tagsNo
titleNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
exercisesNo
difficultyNo
visibilityNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, so the safety profile is known. The description adds the confirm-gating trait, but that is already spelled out in the schema's confirm parameter description ('Must be true to actually execute... returns a preview only'), so the added value is modest. Nothing is said about whether omitted fields are preserved or whether list fields replace wholesale.

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?

Two short clauses, front-loaded with the action and immediately followed by the key operational constraint. No filler or redundancy.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter mutation with no output schema and near-zero schema documentation, the description leaves essential questions unanswered: whether exercises replaces or merges, whether clearing a field is possible, and what a preview response contains. It is too thin for this complexity.

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

Parameters2/5

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

Schema description coverage is only 11% across 9 parameters, so the description must carry the load, and it only partially does: it explains the patch-style partial update and confirm gating, but says nothing about goal/difficulty/visibility enums, tags, or the free-form exercises array whose item shape is entirely unspecified.

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 and resource: 'Edit an existing workout plan template', which cleanly separates it from create_/delete_/get_workout_plan_template siblings. It does not distinguish itself from the adjacent update_workout_plan or update_workout_section_template, so it stops short of full sibling differentiation.

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 phrase 'Only send the fields that change' implies partial-update usage and 'confirm-gated' hints at a preview step, but neither tells the agent when to choose this over update_workout_plan or how to handle a preview result. Usage is implied rather than stated.

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.