Skip to main content
Glama

get_workout_templates

Read-onlyIdempotent

List workout templates as a high level summary: workout_id, name, folder, and exercise count, plus total_count. A workout_id names its workout wherever a workout is read or changed. Returns at most limit templates (default 50, max 200); total_count indicates when the list was truncated. Optional folder_id filters by folder. Does not include individual exercises or sets. Ids are for tool calls only; never show them to the user.

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": "get_workout_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax templates to return (default 50, max 200)
folder_idNoOptional folder_id to filter by, as the folder list gives it

Output Schema

NameRequiredDescriptionDefault
templatesYes
total_countYesTotal templates matching the filter, before the limit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / folder_id
      Added value: +{
      +  "description": "Optional folder_id to filter by, as the folder list gives it",
      +  "type": "string"
      +}
    • removedInput schema / properties / folder_name
      Removed value: -{
      -  "description": "Optional folder name to filter by",
      -  "type": "string"
      -}
    • addedOutput schema / properties / templates / items / properties / folder_id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / templates / items / properties / workout_id
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / templates / items / required
      Previous value: -[
      -  "name",
      -  "exercise_count"
      -]New value: +[
      +  "workout_id",
      +  "name",
      +  "exercise_count"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavior beyond that: the default and maximum limit, the fact that total_count signals truncation, and an unusual presentation constraint ("never show ids to the user") that an agent could not infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the purpose and return shape, followed by pagination, then filtering, then exclusions and the id-handling rule. There is no filler and every sentence contributes a distinct fact.

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

Completeness5/5

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

An output schema exists, so return values need not be detailed here, and the description still summarizes them accurately. For a two-parameter read-only list tool, the description covers scope, pagination, filtering, exclusions, and id handling with nothing an agent would need missing.

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?

Schema description coverage is 100%, and both parameters are already documented there, including the default and max for limit. The description restates the same limit bounds and folder filtering without adding new syntax or edge-case meaning, so it sits at the baseline for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ("List workout templates") and enumerates exactly what comes back: workout_id, name, folder, exercise count, total_count. It also states a negative boundary ("Does not include individual exercises or sets"), which lets an agent separate it from the detail-level workout readers without opening another schema.

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

Usage Guidelines4/5

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

It establishes the use case clearly (high-level browsing of templates, with folder_id to narrow) and rules out detail-oriented use by noting exercises and sets are excluded. What it lacks is an explicit pointer to the sibling that returns full detail, so the exclusion is implied routing rather than a named alternative.

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.

Resources