Skip to main content
Glama

list_workout_section_templates

Read-only

Saved workout sections (e.g. a standard warm-up or finisher) the coach drops into plans. Optional name search.

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

Input Schema

NameRequiredDescriptionDefault
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 structurally. The description adds that this is a saved/reusable library and that searching is optional, but says nothing about result ordering, limits, or how the search matches. Modest added value on top of annotations.

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 tight sentences with the resource definition front-loaded and the parameter hint second; no filler. The trailing fragment "Optional name search." is terse but reads cleanly.

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 simple read-only list with one optional argument and no output schema, the description covers what the resource is and that search is optional. It leaves gaps an agent would care about: what a returned item looks like (no output schema exists to cover this) and whether results are paginated or capped.

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

Parameters3/5

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

The single parameter has 0% schema description coverage, so the description carries the burden; "Optional name search" does tell the agent that `search` filters by name and need not be supplied. It stops short of describing matching behavior (substring vs prefix, case sensitivity) or whether an empty search returns everything.

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 the resource precisely: "Saved workout sections (e.g. a standard warm-up or finisher) the coach drops into plans" makes clear these are reusable section templates rather than plans or logs, and the concrete examples disambiguate against siblings like list_workout_plan_templates. The list verb is only implied by the name rather than stated in the description, which keeps it short of a 5.

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?

There is no explicit when-to-use or when-not guidance and no named alternative, despite a large sibling set containing plan-template lists and section create/update/delete tools. "The coach drops into plans" hints at the reuse workflow but never tells an agent when to call this versus list_workout_plan_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.