Skip to main content
Glama

browse_exercise_catalog

Read-only

Browse/filter the exercise catalog (platform + the coach's own custom exercises) by body part, equipment, discipline or text. Use search_exercises for a quick name lookup; this is for 'show me all dumbbell shoulder moves'. Page with page/pageSize until hasMore is false.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
filterNo
pageSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/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 real behavior beyond that: the result set spans platform plus custom exercises, and pagination is signaled by a hasMore flag in the response. It stops short of describing result ordering or defaults, so it is strong but not exhaustive.

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?

Three front-loaded sentences: scope first, sibling routing second, pagination protocol last. Every sentence adds information an agent needs to call the tool correctly, with no filler.

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

Completeness4/5

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

For a nested-object tool with eight filter fields and no output schema, the description gives enough to call it sensibly and to know when to stop paginating. The gaps around array-vs-scalar filter fields and customOnly keep it from being fully complete.

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 0%, so the description carries the burden, and it does map the filter intent to body part, equipment, discipline, and text. However, it does not explain the singular/plural pairs in the schema (bodyPart vs bodyParts, equipment vs equipments), the customOnly flag, or the page defaults, so meaningful ambiguity remains.

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?

States a specific verb (browse/filter) and resource (exercise catalog), and defines the union of data covered: platform exercises plus the coach's own custom ones. It explicitly contrasts with search_exercises, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative tool (search_exercises) and the condition that selects it ('quick name lookup'), then gives a concrete exemplar query for when this tool is right ('show me all dumbbell shoulder moves'). It also states the iteration protocol (page/pageSize until hasMore is false), leaving nothing to inference.

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.