Skip to main content
Glama

List exercises

list_exercises
Read-onlyIdempotent

Returns the exercise catalog: id, name, kind (the block kind it goes in: back (shown to the athlete as Foundation), strength or mobility; an older exercise without one can only go in an other block), equipment, whether it's loaded, the body areas it stresses, its no-kit and gentle alternatives (suggestions for you; the app never swaps), whether the athlete has reviewed it, and its conservative start prescription if any. A mobility exercise also has style: dynamic (moving through range, good before training), static (a held stretch, good after training or at the end of the day) or release (rolling; the library's roller exercises need a foam roller). An exercise you added earlier may have no style. sides says how it uses the two sides: together (both at once, e.g. a both-arms raise; prescribe bothSides: false) or each (one side per set; prescribe bothSides: true). Writes that contradict it are rejected. No sides means either works (movements that alternate within a set, or an exercise whose ladder levels change it). hasGuide says whether the athlete can read a how-to for it, hasVideo whether the exercise has its own demo video, and hasOwnVideo whether a demo was chosen for this athlete (set_exercise_video), which the app plays instead. library: true marks a built-in exercise whose guide and video you can't change; update_exercise is for library: false ones, the exercises you added, and can add a missing guide to one of those. Sessions must use these ids; add_exercise adds an exercise that isn't listed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover only the safety profile (readOnly/idempotent/non-destructive), and the description adds substantial behavior beyond that: alternatives are suggestions the app never swaps, writes that contradict `sides` are rejected, and library exercises have immutable guides/videos. This is exactly the kind of constraint an agent needs before prescribing from the catalog.

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

Conciseness3/5

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

Every clause carries real information and the field list is front-loaded, but it is delivered as one dense run-on paragraph mixing field semantics, coaching advice, and tool routing. Readability suffers and the routing guidance is buried at the end.

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?

There is no output schema, so the description must document return values, and it does so exhaustively — including edge cases like a missing `sides` or a `style`-less custom exercise. Nothing an agent needs to interpret the catalog is missing.

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?

Zero parameters, so the schema carries nothing and the baseline is 4. The description compensates by documenting the meaning of every returned field (`kind`, `style`, `sides`, `hasGuide`/`hasVideo`/`hasOwnVideo`, `library`, start prescription), which is the functional equivalent here.

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?

Opens with a specific verb and resource ("Returns the exercise catalog") and immediately clarifies scope with "add_exercise adds an exercise that isn't listed" plus a note that update_exercise targets `library: false` entries. An agent can distinguish it from add_exercise/update_exercise/set_exercise_video without opening any 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?

Gives a strong implicit trigger: "Sessions must use these ids," which tells the agent to call this before building sessions, and routes the alternatives (add_exercise for unlisted exercises, update_exercise only for non-library ones, set_exercise_video for demos). It lacks an explicit when-not-to-call statement or pagination/filter behavior, so it stops short of a 5.

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