Wellness Project

delete_workout

DestructiveIdempotent

Saved workout operations

Performed new session: in-app chat uses propose_workout (review card; Save logs); external MCP and native voice use log_workout. Correction to a stored session: update_workout, not another log. Entire-session deletion: delete_workout, not an update. In-app future workouts use proposal tools; external clients without proposal cards may use log_workout(save_as_saved_workout=true) for a reusable template. saved_workout_id selects a template, never a completed session.
Resolve by a known session ID or an unambiguous date/name; ambiguous sessions, sets or superset slots require exact identification. Never invent IDs. Validate all parts of an update before writing; preserve everything outside the target.
Remove one set/exercise through a targeted update; remove the entire session only when requested. Deletions are irreversible. Confirm only successful persisted changes; for partial/uncertain writes, read back before any retry.

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

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

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.7/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds substantial context beyond them: deletions are irreversible, the session plus all supersets and sets are removed, an ambiguous match returns an error with nothing deleted, and partial/uncertain writes should be read back before retrying. It also notes that a known session ID needs no preliminary list call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is useful but the core purpose statement does not appear until the third paragraph, behind a large block of cross-tool routing boilerplate. Irreversibility is stated three separate times ('Deletions are irreversible', 'This action is irreversible and removes...', plus the callout lead), which costs space without adding information.

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 4-parameter tool with full annotation coverage and an output schema, the description covers everything an agent needs: intent routing, ID-vs-date resolution, ambiguity failure behavior, irreversibility, and the saved-workout branch. Return-value explanation is correctly left to the output schema.

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 description coverage is 100%, so the baseline is 3; the description still adds meaning by specifying that session_date defaults to today, that name is only applied when more than one session was logged that day, and that saved_workout_id deletes the reusable prescription rather than workout history. It reinforces the 'never invent IDs' constraint but repeats some schema text.

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 states the specific verb+resource ('Permanently delete a workout session and all its exercises and sets') and explicitly distinguishes this tool from its nearest siblings: whole-session deletion is delete_workout 'not an update', and correction goes to update_workout instead. It also separates completed-session deletion from Saved Workout deletion via saved_workout_id, so an agent can route correctly without opening schemas.

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 gives explicit when-to-use rules (remove a logged workout entirely, remove the entire session only when requested) and when-not rules (use update_workout for corrections, targeted updates for single sets/exercises). It also names the correct alternatives for adjacent intents (propose_workout, log_workout, update_workout) and states the disambiguation rule for multiple sessions on one date.

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.