Wellness Project

delete_workout

DestructiveIdempotent

Permanently delete a workout session and all its exercises and sets. Use when the user wants to remove a logged workout entirely.

FIND THE SESSION: call directly, no preliminary list for an ID. Pass session_id if already known. Otherwise pass session_date (YYYY-MM-DD, defaults to today) and, only if more than one session was logged that day, name (a substring of the workout's focus/type, e.g. "Push" or "Leg Day", case-insensitive) to narrow it down. This action is irreversible and removes the session, all supersets, and all sets — a match that isn't exactly one session returns an error explaining why, with nothing deleted; retry with session_id or a narrower name, never guess.

SAVED WORKOUTS: pass saved_workout_id to delete a reusable Saved Workout instead of completed workout history.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Substring of the workout's focus/type (e.g. "Push", "Leg Day"), case-insensitive, to disambiguate multiple sessions on the same date. Only used when session_id is omitted.
`session_id`	No	Positive session ID returned by a workout tool. If unknown, omit it and use session_date + name; never guess.
`session_date`	No	Date the session was logged. Format: YYYY-MM-DD. Used with name to find the session when session_id is omitted; defaults to today if both are omitted.
`saved_workout_id`	No	Saved Workout ID to delete. When present, deletes the reusable prescription and does not touch completed workout history.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Human-readable result text returned by the tool.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 12, 2026

changedInput schema / properties / session_id / description

Previous value: -"Session ID, if already known. Alternative to session_date + name — see FIND THE SESSION above."New value: +"Positive session ID returned by a workout tool. If unknown, omit it and use session_date + name; never guess."

addedInput schema / properties / session_id / minimum
```
Added value: +1
```

Changed5 schema fields changedSep 7, 2026

addedInput schema / properties / name

Added value: +{
+  "description": "Substring of the workout's focus/type (e.g. \"Push\", \"Leg Day\"), case-insensitive, to disambiguate multiple sessions on the same date. Only used when session_id is omitted.",
+  "type": "string"
+}

addedInput schema / properties / saved_workout_id

Added value: +{
+  "description": "Saved Workout ID to delete. When present, deletes the reusable prescription and does not touch completed workout history.",
+  "type": "integer"
+}

addedInput schema / properties / session_date

Added value: +{
+  "description": "Date the session was logged. Format: YYYY-MM-DD. Used with name to find the session when session_id is omitted; defaults to today if both are omitted.",
+  "type": "string"
+}

changedInput schema / properties / session_id / description

Previous value: -"Session ID from list_workouts. Required — do not proceed without it."New value: +"Session ID, if already known. Alternative to session_date + name — see FIND THE SESSION above."

removedInput schema / required
```
Removed value: -[
-  "session_id"
-]
```

First observedAug 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations mark destructiveHint=true and idempotentHint=true, but the description goes well beyond: it states the action is irreversible, removes the session, all supersets, and all sets, and explains that a non-exact match returns an error with nothing deleted. It also clarifies that saved_workout_id does not touch completed workout history, providing full behavioral disclosure.

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?

The description is well-structured with clear sections: the core purpose, 'FIND THE SESSION' instructions, and 'SAVED WORKOUTS' alternative. It front-loads the primary use case, then provides necessary lookup steps, and every sentence adds value without redundancy.

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 tool with multiple targeting methods, the description covers irreversibility, error behavior, parameter interactions, and the alternative mode for saved workouts. An output schema exists, so return values are presumably documented elsewhere. No critical information is missing for an agent to call it 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 coverage is 100%, so each parameter already has a description. The tool description adds crucial usage logic: session_id is preferred and never to be guessed, session_date defaults to today, name is a case-insensitive substring for disambiguation, and saved_workout_id switches the operation to delete a reusable prescription. This clarifies parameter interactions beyond the schema.

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?

The description clearly states the tool permanently deletes a workout session and all its exercises and sets, which is a specific verb+resource. It also distinguishes between deleting a logged session and a reusable Saved Workout, making it distinct from sibling delete_* tools like delete_cycle or delete_meal.

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?

It explicitly says 'Use when the user wants to remove a logged workout entirely' and provides a detailed decision path: pass session_id if known, otherwise session_date and name for disambiguation, and saved_workout_id for the reusable prescription. It also warns against guessing and directs retries with a narrower name or session_id.

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

All Wellness Project 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.