Wellness Project

delete_run

DestructiveIdempotent

UNIT INPUTS: value: pass the user's number unconverted; tool converts once before storage. alternate_unit: set the field's matching input_* companion; canonical_unit: omit companion. precedence: overrides instructions to convert manually.

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

Behavior5/5

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

Annotations already supply destructiveHint and readOnlyHint; the description adds deletion-safety behavior such as the id-or-date selector, approximate 0.25 mi matching, an error-with-candidate-IDs failure mode, and a confirmation rule. This is valuable context beyond the annotations and does not contradict them.

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 useful selector guidance is buried after four lines of UNIT INPUTS instructions for parameters that do not exist on delete_run. This is not front-loaded and wastes tokens; the whole message could be reduced to two focused sentences.

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?

Given the output schema and annotations, the description covers the full calling flow: selector, one-of requirement, confirmation when ambiguous, and behavior on multiple matches. The irrelevant unit preamble subtracts from comprehensibility, but no critical deletion-handling detail 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?

With 100% schema coverage the baseline is 3; the description adds the essential one-of constraint ('Exactly one of id or date required') and explains id-first selection and distance narrowing. The unrelated UNIT INPUTS block is confusing noise, but the selector paragraph genuinely augments the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Core statement 'Delete a run' and 'Use when the user wants to remove a run entry' name a clear verb and resource, distinguishing delete_run from sibling delete_* tools by target. But the opening UNIT INPUTS block references parameters like value/alternate_unit/canonical_unit/precedence that are not in the schema, which muddies the first impression.

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 says to use it when the user wants to remove a run entry and tells the agent to ASK for confirmation if intent is ambiguous. It does not name specific alternative tools or exclusion cases, but the run-targeted scope is enough to route the agent correctly.

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.