MoveMate: Gym Workout Tracker

Update planned workout

update_planned_workout

DestructiveIdempotent

Changes a workout that has not been done yet — reschedule it, rename it, or replace its exercise list. Works on an upcoming session and on one the app marked skipped because its time passed; rescheduling a skipped session makes it upcoming again. A finished workout cannot be changed. Pass only the fields you want to change; anything omitted stays as-is. exercises, if given, replaces the whole list — to add an exercise, pass the existing ones plus the new one; to remove one, pass the list without it. Because the list is replaced wholesale, any superset_group labels left out are removed too. A workout can mix strength and conditioning freely: each exercise is measured by its own exercise_type (from search_exercises), so a run, a skipping round or a set of sprints sits in the same list as the lifts — send the targets that type accepts.

Input Schema

TableJSON Schema

Name	Required	Description
`notes`	No	New note for the whole session. Send an empty string to clear it; omit to keep the current one.
`title`	No	New workout name. Omit to keep the current one.
`reminder`	No	Push reminder for this session, as an offset before it starts — "oneHour" is one hour before, "thisDay" fires at the workout time itself, "none" removes an existing reminder. Omit it to leave the current setting alone. A reminder needs the session to have a time of day.
`exercises`	No	Replaces the ENTIRE exercise list — send every exercise the workout should keep, not only the changed ones. Omit to keep the current exercises.
`workout_id`	Yes	From create_planned_workout or list_planned_workouts — never invented.
`scheduled_for`	No	ISO 8601 date or datetime as local wall-clock time in the user's own timezone, with NO offset — '2026-08-29T21:00:00' for 9pm where the user lives. A trailing 'Z' or numeric offset is accepted and converted, but plain local time is preferred.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`title`	Yes
`locale`	Yes
`web_url`	Yes
`warnings`	No
`deep_link`	Yes
`total_sets`	Yes
`workout_id`	Yes
`scheduled_for`	Yes
`exercise_count`	Yes
`display_warnings`	No
`estimated_duration_min`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, but the description adds substantive behavior: a skipped session becomes upcoming again when rescheduled, `exercises` is a wholesale replacement, and omitted superset_group labels are dropped. These are destructive side effects an agent could not infer from the annotations alone.

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 the core action and organized as one dense, informative paragraph with no filler. It is on the longer side, and the closing sentence about mixing strength and conditioning is somewhat discursive, but nearly every clause carries operational weight.

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 destructive, idempotent patch-style mutation on a nested exercise structure, the description covers eligibility, replacement semantics, label loss and unit/target conventions. An output schema exists, so return-value explanation is unnecessary, and nothing an agent needs to call it correctly is missing.

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 coverage is 100% so the baseline is 3, but the description adds cross-parameter semantics the schema only states locally: the replace-whole-list rule for exercises ('to add an exercise, pass the existing ones plus the new one'), the loss of superset_group labels on omission, and the exercise_type-driven target selection across mixed strength/conditioning lists.

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 ('Changes a workout that has not been done yet') and enumerates what can change: reschedule, rename, replace exercise list. An agent can distinguish this from create_planned_workout and delete_planned_workout without opening any 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?

Explicitly defines the eligible states (upcoming session, or one the app marked skipped because time passed) and the exclusion ('A finished workout cannot be changed'). It also gives the patch contract explicitly ('Pass only the fields you want to change; anything omitted stays as-is'), which removes the main ambiguity for an update tool.

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?