Wellness Project MCP

delete_lab_result

DestructiveIdempotent

Permanently remove logged lab results. Delete a single marker using its ID, or remove an entire blood draw by date; narrow with panel or marker when needed.

Instructions

Permanently delete one or more lab results. Use when the user explicitly asks to remove or delete a logged lab result. Never guess a selector.

SELECTOR, pass exactly one of id, date, or date+marker:

id: deletes a single marker's row.
date (optionally narrowed by panel_name): deletes every result from that draw at once. This is irreversible and can remove many rows in one call. Confirm with the user before a date-scoped delete, especially one not narrowed by panel_name or marker.
date + marker (a marker-name substring, case-insensitive, optionally narrowed by panel_name): resolves to and deletes one marker's row, same as id. Errors with candidate IDs if more than one marker on that date matches.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_lab_result"
  }
}

Input Schema

Name	Required	Description
`id`	No	Lab result ID. Deletes a single marker row. Alternative to date.
`date`	No	Collection date of the draw to delete. Format: YYYY-MM-DD. Deletes every result from that draw, or (with marker) one row. Alternative to id.
`marker`	No	Optional with date: marker-name substring, case-insensitive (e.g. "LDL"), narrowing the date selector to delete a single marker row instead of the whole draw. Ignored when id is given.
`panel_name`	No	Optional, narrows a date (or date+marker) selector to one panel within that draw (e.g. "Lipid Panel"). Ignored when id is given.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Sep 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing that date-scoped deletes are irreversible, can remove many rows at once, and require user confirmation. It also includes the strong guardrail 'Never guess a selector.' These behaviors are not inferable from readOnlyHint=false or destructiveHint=true alone, so the description adds substantial value.

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 a bolded selector heading and bullet-like separators. Every sentence serves a purpose: defining the action, stating when to use it, warning about irreversibility, and explaining parameter combinations. The length is appropriate for the destructive and ambiguous nature of the operation.

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?

Given the tool's destructive nature and four optional parameters with complex interactions, the description fully covers what an agent needs: when to use it, how to choose selectors, what is irreversible, and when to confirm with the user. The output schema exists, so return-value documentation is not required. No critical context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description enriches the parameters by explaining the selector hierarchy: id deletes one row, date deletes the whole draw, and date+marker resolves to one row with error behavior if multiple markers match. It also clarifies that panel_name narrows date-based selectors and that marker is ignored when id is present—none of which the schema alone conveys as clearly.

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 opens with 'Permanently delete one or more lab results,' which is a specific verb and resource. It also clarifies the exact use case ('when the user explicitly asks to remove or delete a logged lab result') and distinguishes itself from siblings by focusing on deletion rather than update or logging.

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?

The description explicitly states when to use the tool and provides detailed selection guidelines among id, date, and date+marker. It does not explicitly name alternatives like update_lab_result for non-destructive corrections, but the context is clear enough that an agent should not confuse this with other lab-related tools.

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

Deploy Server