Skip to main content
Glama

wger

by io.github.pipeworx-io

List Exercises

list_exercises
Read-onlyIdempotent

List fitness exercises from the wger database in English; optionally limit count (default 20). Returns exercise name, description, category, primary and secondary muscles, and required equipment per entry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of exercises to return. Defaults to 20.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesTotal number of exercises in the database
exercisesYes

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already signal read-only and idempotent behavior, so the bar is lower. The description adds transparency about the default limit of 20 and the language filter (English), which are not evident from annotations or schema.

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?

The description is two sentences, with the main action stated first and supplementary details (default count, return fields) following. Every word adds value without fluff.

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?

Given the tool's simplicity (one optional parameter), rich annotations, and existing output schema, the description covers all essential aspects: purpose, scope, return content, and default behavior. No significant gaps remain.

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 schema already covers the single 'limit' parameter with full coverage. The description reinforces the default value but introduces no new syntax or semantics beyond the schema, aligning with the baseline for high schema coverage.

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?

Description specifies the verb 'List' and the resource 'fitness exercises from the wger database', with a clear scope (English, optional limit). It differentiates from siblings like get_exercise by indicating a list of entries with multiple muscle and equipment fields.

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?

The description provides clear context for when to use the tool (fetching a list of exercises from wger) and implicitly distinguishes it from more specific tools like get_exercise. It does not explicitly state exclusions or mention sibling alternatives, which prevents a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All wger toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Many tools have detailed, differentiated roles, but there are several overlapping clusters: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all answer natural-language data questions, and ask_pipeworx_beta is currently identical to ask_pipeworx. Onboarding/discovery and Polymarket edge tools also blur together, so an agent can easily select the wrong entry point.

Naming Consistency3/5

Names are uniformly snake_case and readable, with coherent subfamilies like ask_pipeworx*, polymarket_*, and list_*. But conventions are mixed across the set: bare verbs (remember, forget, subscribe), noun phrases (entity_profile, recent_changes), and adjective-led names (recent_alerts) exist alongside verb_noun names, so there is no consistent pattern.

Tool Count2/5

35 tools is already in the 'too many' range, and only four (get_exercise, list_exercises, list_equipment, list_muscles) belong to a wger fitness server. The remaining ~31 tools are unrelated Pipeworx/prediction-market/memory utilities, making the count inappropriate for the apparent domain.

Completeness1/5

As a wger fitness server, the surface is a read-only reference slice: exercise, equipment, and muscle lookups, with no workout routine management, user data, or create/update/delete operations for any wger resource. Even ignoring the unrelated Pipeworx tools, the fitness domain has severe gaps that would block most real usage.

Resources