Skip to main content
Glama

MoveMate: Gym Workout Tracker

by app.movemate
OverviewDiscussionsAdmin

List workouts

list_workouts
Read-only

Browses MoveMate's workout catalog — both the shared library and the user's own custom workouts, together by default. Use this to find an existing workout to schedule (pass its workout_id to create_planned_workout) rather than building one from scratch, to find one of the user's saved workouts to change (update_custom_workout, after reading it with get_workout_details), to browse by body focus ("give me a leg workout" — use category), or to look up one the user just opened in the app by its workout_id. Not the user's calendar (see list_planned_workouts) and not training history (see get_recent_workouts).

Input Schema

NameRequiredDescriptionDefault
typeNoRestrict to only the shared library or only the user's own custom workouts. Omit for both.
limitNoHow many workouts to return. Default 20, max 50.
queryNoMatches workout titles and exercise names inside them — e.g. "push day" (a title) or "deadlift" (finds any workout containing it, even if the title doesn't mention it).
categoryNoBody focus, style, or goal — e.g. "legs", "upper body", "full body", "core", "cardio", "hiit", "strength", "bodyweight", "stretching", "muscle gain", "get shredded", "recovery", "home workout", "beginner". Use this for "give me a leg workout"-style requests; use query instead for a specific exercise or title. Not for own/saved workouts — use type: "custom" for those.
workout_idNoLook up one specific workout by its id — from an earlier result, a deep link, or context the app handed off. Overrides query.

Output Schema

NameRequiredDescriptionDefault
totalYesTotal workouts matching the filter, which can exceed the returned list — narrow with query or type if it does.
localeYes
workoutsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / workouts / items / properties / content_summary
      Added value: +{
+  "description": "Compact catalog tags used to compare muscle emphasis, goal, and duration when selecting a program.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / workouts / items / required
      Previous value: -[
-  "workout_id",
-  "title",
-  "type",
-  "duration_min",
-  "fitness_level",
-  "exercises",
-  "exercise_count",
-  "is_premium",
-  "image_url",
-  "deep_link",
-  "web_url"
-]New value: +[
+  "workout_id",
+  "title",
+  "type",
+  "duration_min",
+  "fitness_level",
+  "content_summary",
+  "exercises",
+  "exercise_count",
+  "is_premium",
+  "image_url",
+  "deep_link",
+  "web_url"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's main behavioral addition is that library and custom results are merged by default, but the schema's `type` parameter already says 'Omit for both.' It adds no return shape, ordering, or pagination behavior beyond that.

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

Conciseness4/5

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

Dense but front-loaded: the core purpose lands in the first clause, followed by usage routing and exclusions. The long parenthetical list of use cases is efficient, though the single-sentence structure makes it slightly harder to scan than it could be.

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 described. The description covers purpose, the merged-source default, parameter routing, downstream follow-ups, and the two nearest alternatives — everything an agent needs to select and invoke this tool correctly.

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?

Schema description coverage is 100%, so the baseline is 3, but the description goes further by tying parameters to workflows: category for body-focus requests vs query for exercise/title matches, and workout_id for deep links or handoff context passed to create_planned_workout. This cross-parameter routing guidance is meaningfully more than the schema alone.

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 and resource ('Browses MoveMate's workout catalog') and immediately scopes it to the two underlying sources (shared library plus the user's custom workouts). It explicitly names the sibling tools it is not (list_planned_workouts, get_recent_workouts), so an agent can distinguish it without opening a 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?

Gives four concrete use cases with the follow-up tool for each (pass workout_id to create_planned_workout, update_custom_workout after get_workout_details, category for 'give me a leg workout', workout_id for a recently opened workout). It also states the two exclusions explicitly and routes to the correct alternatives.

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

All MoveMate: Gym Workout Tracker toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources