Skip to main content
Glama

list_workout_plan_templates

Read-only

List the coach's workout plan templates (id, title, tags, difficulty, goal).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_workout_plan_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
searchNo
onlyMineNo
pageSizeNo
pageNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the returned field set (id, title, tags, difficulty, goal), which is useful, but says nothing about pagination behavior, total counts, filtering semantics, or ordering.

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?

One tightly written sentence, front-loaded with the verb and resource with zero filler. The trailing parenthetical earns its place by conveying return fields, though it is easily mistaken for a parameter list.

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?

With five undocumented parameters, no output schema, and no explanation of filtering or paging, the definition leaves too much for the agent to infer. Naming return fields helps slightly, but the call contract is still under-specified for a filterable list tool.

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 0% across five parameters, and the description does not compensate: tag, search, onlyMine, pageSize, and pageNumber are never mentioned. The parenthetical lists response fields rather than explaining what the filters do, so an agent must guess at filter semantics and defaults.

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 (List) and resource (coach's workout plan templates), and the parenthetical names the fields returned. It implicitly contrasts with list_workout_plans and get_workout_plan_template via the word 'templates', though it never explicitly distinguishes them.

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

Usage Guidelines2/5

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

No guidance on when to use this versus get_workout_plan_template, list_workout_plans, or the other list_*_templates siblings, and no exclusions or prerequisites. Usage is only inferable from the verb 'List' itself.

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.