Skip to main content
Glama
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

icu_delete_gear

DestructiveIdempotent

Permanently remove a gear item and its associated maintenance reminders without affecting past activities that used it.

Instructions

Permanently delete a gear item and its maintenance reminders. Activities that used this gear are not affected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gear_idYesID of the gear item to delete
athlete_idNoAthlete ID (for coaches managing multiple athletes)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / athlete_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Athlete ID (for coaches managing multiple athletes)"
+}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already indicate destructive=true, idempotent=true, and readOnly=false. The description adds crucial context not covered by annotations: the deletion is permanent, it cascades to maintenance reminders, and it does not affect activities. This is valuable behavioral detail, though it doesn't mention authentication, rate limits, or recovery options.

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?

Two concise sentences, front-loaded with the core action and followed by an important clarification. Every sentence earns its place with no redundancy.

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 the presence of an output schema, the description provides all necessary context: it confirms permanence, mentions the cascade to reminders, and clarifies that activities are unaffected. The annotations and output schema cover the rest.

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 both parameters. The description does not add any parameter-specific information beyond what the schema provides, which is the baseline expectation (3) when schema coverage is high.

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 a specific verb ('Permanently delete'), a specific resource ('gear item'), and explicitly scopes the effect ('and its maintenance reminders' / 'Activities that used this gear are not affected'). This distinguishes it from sibling tools like icu_update_gear and icu_create_gear_reminder.

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 clearly conveys when to use this tool (to delete a gear item) and the scope of the deletion, including that activities are unaffected. However, it does not mention alternatives (e.g., archiving vs. deleting) or prerequisites, so it falls short of a 5.

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

Deploy Server

Other Tools