io.github.hhopke/intervals-icu-mcp

icu_delete_workout

DestructiveIdempotent

Delete a single library workout permanently. Removes the workout from your library; calendar events require separate deletion.

Instructions

Permanently delete ONE workout from the LIBRARY. Destructive — cannot be undone.

Removes the library workout only; calendar events are separate records deleted with icu_delete_event. Confirm with the user before calling if unsure.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`athlete_id`	No	Athlete ID (for coaches managing multiple athletes)
`workout_id`	Yes	Library workout ID to delete (from icu_get_workouts_in_folder)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Even though destructiveHint is already set, the description adds important context: the deletion is permanent and cannot be undone, it applies only to library workouts, and it does not delete associated calendar events. This goes beyond the annotation by clarifying exactly what gets destroyed and what does not.

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?

Three short sentences with no filler. The destructive nature is front-loaded, followed by scope and the relevant alternative. Every sentence earns its place.

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 simple two-parameter destructive tool with a full output schema and supportive annotations, the description covers what is deleted, what is not deleted, how to delete related records, and a user-confirmation safeguard. Nothing essential is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents workout_id and athlete_id. The description does not add new parameter-level meaning beyond confirming the singular 'ONE workout' target, but it also does not need to compensate for schema gaps.

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 exact verb and resource: 'Permanently delete ONE workout from the LIBRARY.' It also clearly distinguishes this from calendar-event deletion, which is handled by a different tool, so there is no ambiguity about what this tool operates on.

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?

The description explicitly says when to use this tool versus alternatives: it deletes library workouts only, while calendar events must be deleted with icu_delete_event. It also instructs the agent to confirm with the user before calling if unsure, which is a clear usage safeguard.

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

Deploy Server