Wellness Project

delete_run

DestructiveIdempotent

UNIT INPUTS: never convert units yourself. For each canonical field below, pass the user's number exactly as stated when it is already in the canonical unit; when they gave the alternate unit instead, pass the same number unconverted and set the matching companion field so the tool converts once before storage. Omit the companion when the number is already canonical. This overrides any wording that asks you to do the arithmetic.

_lb fields: lb, or kg with input_weight_unit set.
_mi fields: mi, or km with input_distance_unit set.
_in fields: in, or cm with input_length_unit set.
_stated_g fields: g, or oz with input_mass_unit set.
_stated_ml fields: ml, or fl_oz with input_volume_unit set.

Delete a run. Use when the user wants to remove a run entry. ASK for confirmation if the user's intent is ambiguous.

SELECTOR — pass id if known, or date (+ optional distance_mi to narrow, matched approximately within 0.25 mi) to resolve it. Exactly one of id or date required. If it matches more than one run, the call errors with candidate IDs to retry with.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Run UUID. Alternative to date.
`date`	No	Alternative to id: the date (YYYY-MM-DD) the run was logged on. Optionally narrow with distance_mi.
`distance_mi`	No	Optional, narrows date to a run within 0.25 mi of this value when more than one run shares that date. Ignored when id is given. In mi, or km with input_distance_unit set. See UNIT INPUTS.
`input_distance_unit`	No	Set to km when the user gave km for the _mi fields in this object. Omit when they are already mi.

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.

Changed5 schema fields changedSep 7, 2026

addedInput schema / properties / date

Added value: +{
+  "description": "Alternative to id: the date (YYYY-MM-DD) the run was logged on. Optionally narrow with distance_mi.",
+  "type": "string"
+}

addedInput schema / properties / distance_mi

Added value: +{
+  "description": "Optional, narrows date to a run within 0.25 mi of this value when more than one run shares that date. Ignored when id is given. In mi, or km with input_distance_unit set. See UNIT INPUTS.",
+  "type": "number"
+}

changedInput schema / properties / id / description

Previous value: -"Run UUID from list_runs. Required."New value: +"Run UUID. Alternative to date."

addedInput schema / properties / input_distance_unit

Added value: +{
+  "description": "Set to km when the user gave km for the _mi fields in this object. Omit when they are already mi.",
+  "enum": [
+    "mi",
+    "km"
+  ],
+  "type": "string"
+}

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

First observedAug 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety is covered structurally. The description adds genuine behavior beyond that: it warns the call errors with candidate IDs when the selector matches multiple runs, and it requires confirmation on ambiguous intent. It does not state reversibility or what is destroyed alongside the run.

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

Conciseness2/5

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

The description opens with a large UNIT INPUTS block that is irrelevant to a delete operation except for the single optional distance_mi field, and it buries the actual purpose ("Delete a run") several paragraphs down. The purpose and selector guidance are good but not front-loaded, and the boilerplate dominates the text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with an output schema and full annotation coverage, the description supplies the selector contract, the confirmation requirement, and the multi-match failure path. What remains unspecified is the effect on dependent data and whether deletion is recoverable.

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 per-field docs are already handled. The description still earns credit for adding rules the schema lacks: "exactly one of id or date required", the approximate 0.25 mi narrowing semantics, and the multi-match retry behavior. The long unit-conversion rules also add meaning beyond "mi, or km with input_distance_unit set".

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?

"Delete a run" names a specific verb+resource, and "Use when the user wants to remove a run entry" disambiguates it from the many sibling deleters (delete_workout, delete_cycle, delete_meal). An agent can pick it out immediately from the list.

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?

It gives clear trigger conditions ("remove a run entry") and an explicit caution to ask for confirmation on ambiguous intent. However, it never explicitly routes the agent away from the nearest alternative (e.g. delete_workout, or update for corrections), so the alternative-selection guidance is implied rather than stated.

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.