Skip to main content
Glama

create_workout_plan_template

Save a reusable workout plan template (confirm-gated). exercises follow the same shape as create_workout_plan's.

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": {
      "title": "<title>",
      "visibility": "<visibility>",
      "exercises": "<exercises>"
    },
    "name": "create_workout_plan_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNo
tagsNo
titleYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
exercisesYes
difficultyNo
visibilityYes
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 a non-destructive, non-open-world write, so the safety profile is covered. The "confirm-gated" note is the key behavioral trait, but it largely restates the schema's own confirm parameter description, and the description says nothing about what visibility=PUBLIC implies, side effects, or limits.

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, front-loaded with the action and resource, with no filler. It is efficient, though the terseness leaves the 8-parameter surface largely unexplained.

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 an 8-parameter creation tool with 13% schema description coverage, no output schema, and enum fields whose meaning (e.g., PUBLIC visibility) affects outcomes, the description is too thin. Required fields, defaults, and the result of the default preview mode are left undocumented.

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 coverage is only 13% - just the confirm parameter is documented - yet the description explains none of title, visibility, goal, tags, difficulty, or description. The single hint ("exercises follow the same shape as create_workout_plan's") pushes the agent into another tool's schema rather than documenting the nested item shape here.

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?

"Save a reusable workout plan template" gives a specific verb (save/create) and resource (workout plan template), which distinguishes it from update_/delete_/get_ template siblings. It does not explicitly separate itself from create_workout_plan or create_workout_section_template, so an agent must infer the plan-vs-template boundary.

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 parenthetical "confirm-gated" signals a two-step preview/execute flow, and the cross-reference to create_workout_plan implies when exercise payloads can be reused. There is no explicit statement of when to choose a template over creating an actual plan, nor any prerequisites or exclusions.

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.