Skip to main content
Glama

create_workout_section_template

Save a reusable workout section (warm-up, finisher, circuit) to drop into plans later. ownedByGym: share it with the whole gym (gym owners/admins). (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": {
      "name": "<name>",
      "exercises": "<exercises>"
    },
    "name": "create_workout_section_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
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
exercisesYes[{ name, sets, reps, restSeconds?, exerciseId?, notes?, modality?, supersetGroup?, ... }] — same shape as create_workout_plan exercises; reps can be a range like "8-12".
ownedByGymNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description is not obligated to explain safety, yet it adds two pieces of real behavior: the confirm-gated preview-then-execute pattern and the permission requirement that ownedByGym is limited to gym owners/admins. It still does not say whether a template created this way is immediately available in plans or what the preview response contains.

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 sentences plus a parenthetical, all front-loaded, with the confirm-gating caveat placed last where it belongs. Nothing is padded, though the parenthetical style is slightly terse for a mutation tool.

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?

For a 5-parameter creation tool with no output schema and no annotations covering side effects, the definition is adequate but thin: it never states what comes back from a preview versus a confirmed call, nor whether the new template is automatically visible in plan authoring. The core calling information is present, so it is usable but not complete.

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%, and the description compensates on the weakest spots: ownedByGym gets its actual meaning (share with the whole gym) plus its authorization constraint, which the schema leaves entirely undocumented, and section is illustrated with warm-up/finisher/circuit examples. The name and exercises parameters are left to the schema, which already documents exercises in detail.

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 uses a specific verb ("Save") and a clearly scoped resource ("a reusable workout section"), and concretizes it with examples (warm-up, finisher, circuit). It does not explicitly contrast with create_workout_plan_template or update_workout_section_template, so an agent must infer the section-vs-plan distinction from the resource name alone.

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?

"to drop into plans later" implies the reuse scenario and hints that this is for authoring, not assignment, but there is no explicit when-to-use/when-not guidance and no named alternative such as create_workout_plan_template for full plans or update_workout_section_template for edits to existing templates.

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.