Skip to main content
Glama

MoveMate: Gym Workout Tracker

by app.movemate
OverviewDiscussionsAdmin

Create saved workout

create_custom_workout

Saves a new workout to the user's own workouts ("My workouts" in the app) without putting it on the calendar — a reusable routine such as "Chest day". To also schedule it, pass the returned workout_id to create_planned_workout; to put a one-off session on a date, use create_planned_workout with an exercise list instead. Every exercise_id must come from search_exercises or create_custom_exercise — never invented. Propose the workout and get the user's agreement before calling. Not safe to blindly retry, though an identical call within two minutes returns the workout already saved instead of a second copy. Supersets and circuits are set with the superset_group label on each exercise — see that field for the rule it requires. Each exercise is measured by its own exercise_type (from search_exercises) — send the targets that type accepts. Free accounts can save a limited number of workouts from chat; a refusal for that reason says so and must not be retried.

Input Schema

NameRequiredDescriptionDefault
notesNoOptional note for the whole workout, shown in the app. Max 500 characters.
titleYesWorkout name shown in the app, e.g. "Chest day". Max 60 characters.
exercisesYesThe exercises in the order they are performed — at least one.

Output Schema

NameRequiredDescriptionDefault
totalYesTotal workouts matching the filter, which can exceed the returned list — narrow with query or type if it does.
localeYes
warningsNo
workoutsYes
total_setsYes
workout_idYesThe saved workout — pass it to create_planned_workout to schedule it.
display_warningsNo
upcoming_sessionsYesHow many upcoming scheduled sessions use this workout — they show any change made to it.

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. Changed4 schema fields changed
    • changedInput schema / properties / exercises / items / properties / sets / items / properties / target_distance_m / description
      Previous value: -"Target distance in METRES — 5 km is 5000. Belongs to exercise_type \"distance_time\" and \"weight_distance\". If the user speaks in miles or kilometres, convert here and keep talking to them in their own unit."New value: +"Target distance in METRES — 5 km is 5000. Belongs to exercise_type \"distance_time\" and \"weight_distance\". If the user speaks in miles or kilometres, convert here and keep talking to them in their own unit. Not for \"cardio_machine\": there the distance is derived from speed and duration."
    • changedInput schema / properties / exercises / items / properties / sets / items / properties / target_duration_seconds / description
      Previous value: -"Target duration in SECONDS, for work measured by time: a 20-minute run is 1200, a 45-second plank is 45. Belongs to exercise_type \"time\", \"time_weight\" and \"distance_time\". One timed effort is one set — 8 hill sprints of 30s is 8 sets of 30, not a single set of 240."New value: +"Target duration in SECONDS, for work measured by time: a 20-minute run is 1200, a 45-second plank is 45. Belongs to exercise_type \"time\", \"time_weight\", \"distance_time\" and \"cardio_machine\". One timed effort is one set — 8 hill sprints of 30s is 8 sets of 30, not a single set of 240 — and a steady cardio session is ONE set: 20 minutes on the treadmill is a single set of 1200."
    • addedInput schema / properties / exercises / items / properties / sets / items / properties / target_level
      Added value: +{
+  "description": "The machine's own difficulty number, as shown on its display: incline % on a treadmill, resistance on a bike or stepmill. -20 to 100; 0 is a real setting (flat), negative is decline. Belongs to exercise_type \"cardio_machine\" only. Omit it when the user did not name one.",
+  "maximum": 100,
+  "minimum": -20,
+  "type": "number"
+}
    • addedInput schema / properties / exercises / items / properties / sets / items / properties / target_speed_kmh
      Added value: +{
+  "description": "Target machine speed in KM/H, one decimal — e.g. 10.5. Belongs to exercise_type \"cardio_machine\" only (treadmill, stationary bike, stepmill). If the user speaks in mph, convert here (1 mph = 1.609 km/h).",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}
  3. 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=false, destructiveHint=false and idempotentHint=false, so the mutation profile is covered. The description goes further with a concrete retry behavior — an identical call within two minutes returns the existing workout instead of a duplicate — and a quota refusal that must not be retried, which are genuinely useful operational details. It stops short of describing failure behavior for other error classes.

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?

Front-loads the core purpose and the sibling routing, then layers constraints. It is dense and mostly earns its space, though the exercise_id provenance rule and the exercise_type targeting advice partially duplicate what the schema already says.

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 no explanation, and the description still tells the agent to reuse the returned workout_id. Combined with the retry/quota behavior, sibling routing, and grouping constraints, an agent has everything needed to call this correctly.

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 100%, so the schema already documents every field, including set_type semantics, per-hand weights, and superset_group's positional constraint. The description restates the exercise_id provenance rule that the schema also carries verbatim and points to superset_group without adding syntax, so it earns the baseline 3 rather than more.

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 ("Saves a new workout to the user's own workouts"), identifies the UI location ("My workouts"), and names the sibling it is not ("without putting it on the calendar"), distinguishing it from create_planned_workout and update_custom_workout.

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?

Explicitly routes between alternatives: use create_planned_workout with the returned workout_id to schedule, or with an exercise list for a one-off session. It also states prerequisites (get the user's agreement before calling) and the condition for the free-account refusal and that it must not be retried.

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