MoveMate: Gym Workout Tracker

Delete planned workout

delete_planned_workout

DestructiveIdempotent

Cancels a planned (not yet done) workout and takes it off the schedule. Only affects upcoming planned workouts — a workout already marked done or skipped cannot be removed from chat. Removes only the session: a saved workout it was scheduled from stays in the user's saved workouts. When the same workout is scheduled more than once, pass session_date to pick the session.

Input Schema

Name	Required	Description	Default
`workout_id`	Yes	From create_planned_workout or list_planned_workouts — never invented.
`session_date`	No	The date (YYYY-MM-DD, the date part of scheduled_for in list_planned_workouts) of the session to cancel. Only needed when this workout_id is scheduled more than once; without it the next upcoming session is cancelled.

Output Schema

Name	Required	Description	Default
`deleted`	Yes
`workout_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

addedInput schema / properties / session_date

Added value: +{
+  "description": "The date (YYYY-MM-DD, the date part of scheduled_for in list_planned_workouts) of the session to cancel. Only needed when this workout_id is scheduled more than once; without it the next upcoming session is cancelled.",
+  "type": "string"
+}

First observedOct 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint. The description adds valuable context beyond annotations: the scope limit (only upcoming), that done/skipped workouts are unaffected, and that the underlying saved workout is preserved.

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?

Three sentences, each earning its place, with the core action and main constraint front-loaded before edge cases.

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?

Covers the operation, its limits, side effects on related saved workouts, and the duplicate-schedule case. With an output schema present, no return-value explanation is needed.

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 both parameters are already documented. The description reinforces session_date usage for duplicate schedules but adds no syntax beyond the schema; baseline 3 is appropriate.

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?

Specific verb (cancels/removes) and resource (planned workout), and it clearly distinguishes from siblings like list_planned_workouts and update_planned_workout by describing removal from the schedule.

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?

Explicitly states when it applies (upcoming planned workouts only) and the exclusion (done or skipped cannot be removed from chat), plus the session_date disambiguation for repeated schedules. No explicit alternative tool named, but conditions are clear.

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?