Skip to main content
Glama

wger

by io.github.pipeworx-io

Get Exercise

get_exercise
Read-onlyIdempotent

Get detailed information for a specific exercise by its numeric ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe numeric wger exercise ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesExercise ID
nameYesExercise name
musclesYesPrimary muscles targeted
categoryYesExercise category name or null
equipmentYesEquipment required
descriptionYesExercise description (HTML stripped)
muscles_secondaryYesSecondary muscles targeted

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "description": "Exercise category name or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "description": "Exercise description (HTML stripped)",
+      "type": "string"
+    },
+    "equipment": {
+      "description": "Equipment required",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "id": {
+      "description": "Exercise ID",
+      "type": "number"
+    },
+    "muscles": {
+      "description": "Primary muscles targeted",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "muscles_secondary": {
+      "description": "Secondary muscles targeted",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "name": {
+      "description": "Exercise name",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "description",
+    "category",
+    "muscles",
+    "muscles_secondary",
+    "equipment"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 1
+  },
+  {
+    "id": 42
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which cover the safety profile. The description adds no additional behavioral context (e.g., error handling, caching, or existence requirements) beyond confirming it is a read operation. Since annotations carry the burden, a 3 is appropriate.

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 a single, concise sentence that front-loads the action and resource. No unnecessary words or repetition.

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?

The tool has a single parameter, a rich output schema, and clear annotations. The description fully explains the tool's purpose and input requirement. There is no need for additional detail about return values or behavior since the output schema and annotations cover them.

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 input schema has 100% parameter description coverage: 'The numeric wger exercise ID.' The description's phrase 'by its numeric ID' only restates what the schema already explains, adding no new meaning. Baseline 3 is applied.

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 clearly states the tool's function: 'Get detailed information for a specific exercise by its numeric ID.' It uses a specific verb ('Get'), identifies the resource ('specific exercise'), and distinguishes itself from sibling tools like list_exercises by focusing on individual items.

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 implies the appropriate use case (when you have a numeric ID and need details), which is clear context. However, it does not explicitly exclude alternatives like list_exercises or mention when not to use it, so it falls short of a full 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