MoveMate: Gym Workout Tracker

Log completed workouts

log_completed_workouts

Records workouts the user has ALREADY FINISHED into their MoveMate history — "log yesterday's workout: bench 4x8 at 80 kg, squats 3x5 at 100", or a short history the user is moving over from notes or another app. Send whole sessions with the sets actually done, up to 20 workouts per call. Not a live tracker: if the user wants to log set by set while training, point them to the workout tracker in the MoveMate app (rest timer, weight suggestions) instead of calling this after every set. Dates: a workout from before the user joined MoveMate is history and may have any date; a workout from since they joined must be from today or the last 14 days. For a future date use create_planned_workout. At most 300 past workouts can be moved in through chat in total; for a longer history or an export file from another app (Hevy, Strong and others), tell the user about the workout import in the MoveMate app instead. Every exercise_id must come from search_exercises or create_custom_exercise — never invented. Each exercise is measured by its exercise_type (from search_exercises); send the fields that type uses: default = weight and reps (most strength work, and bodyweight work with reps such as pull-ups or hill sprints); time = duration only (planks, dead hangs, skipping); time_weight = duration and weight (weighted plank, farmer hold); distance_time = distance and duration (outdoor running, cycling or swimming, rowing machine, SkiErg — anything whose monitor shows distance rather than km/h); weight_distance = weight and distance (farmer walk, sled push); cardio_machine = speed in km/h, the machine level (incline or resistance) and duration — treadmill, stationary bike, stepmill; distance is derived from speed and time. Continuous cardio (cardio_machine, distance_time) is ONE set per session — a 20-minute treadmill walk is a single set of 1200 seconds, not three. If you had to guess any exercise, weight, rep count or date, read the workouts back and get the user's agreement before calling. Safe to retry: a workout already in the history (same date, start time and title) is not added twice. Free accounts can finish 3 workouts in total (in the app and here together); workouts from before they joined do not count. A refusal for that reason says so and must not be retried.

Input Schema

Name	Required	Description	Default
`workouts`	Yes	The finished workouts, oldest first. At most 20 per call.

Output Schema

Name	Required	Description
`failed`	Yes
`logged`	Yes	Workouts done since the user joined that were added.
`app_url`	No	Opens the MoveMate app (or its store page) where the logged history is; give it to the user as is.
`history_added`	Yes	Workouts from before the user joined that were added.
`already_logged`	Yes	Workouts that were already in the history and were not added again.
`free_workouts_left`	Yes
`completed_workout_ids`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedOutput schema / properties / app_url

Added value: +{
+  "description": "Opens the MoveMate app (or its store page) where the logged history is; give it to the user as is.",
+  "type": "string"
+}

AddedOct 14, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Far beyond what the annotations say: discloses the 20-workouts-per-call and 300-total-moved limits, the free-account cap of 3 finished workouts, the date-window rules (any date before joining, today or last 14 days after), and that a refusal states its reason and must not be retried. It also gives dedupe semantics ('same date, start time and title' is not added twice), which the agent needs in order to reason about retries.

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-loaded with purpose, then constraints, then field semantics — a sensible order and almost every sentence carries a distinct rule. It is dense, though, packing date rules, quotas, exercise_type mapping and dedupe into one block, so an agent must parse a long paragraph to extract the type-to-field mapping.

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?

For a nested write tool with real quota and date edge cases, nothing essential is missing: identity of the operation, alternatives, per-type field requirements, unit conventions, limits, and failure behavior are all covered, and return values are carried by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even at 100% schema coverage this description adds meaning the schema cannot: it maps each exercise_type (default, time, time_weight, distance_time, weight_distance, cardio_machine) to the specific fields to send, and states that continuous cardio is one set per session rather than three. It also reinforces the exercise_id sourcing rule and the 'read back and confirm if you guessed' discipline that the schema does not express.

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?

Opens with a specific verb and resource ('Records workouts the user has ALREADY FINISHED into their MoveMate history') and immediately scopes it as backfill/history rather than live tracking. It explicitly separates itself from the in-app live tracker and from create_planned_workout, so an agent can pick between them 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 explicit when-to-use examples ('log yesterday's workout: bench 4x8 at 80 kg'), and explicit when-not: not set-by-set during training (point to the in-app tracker), future dates go to create_planned_workout, large histories go to the in-app import. It also names the escalation path for a quota refusal and forbids retrying it.

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 tools Inspect

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

Need Help?