Skip to main content
Glama
Sign In
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Update Gear

icu_update_gear
Idempotent

Update an existing gear item by sending only the fields you change, including name, type, active status, or athlete. Retire or un-retire gear by toggling active status.

Instructions

Update an existing gear item. Only fields you pass are sent.

Input Schema

NameRequiredDescriptionDefault
nameNoUpdated name
activeNoFalse retires the gear (dated today); True un-retires it
gear_idYesID of the gear item to update
gear_typeNoUpdated type, case-insensitive (Bike, Shoes, Trainer, Chain, ...)
athlete_idNoAthlete ID (for coaches managing multiple athletes)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv5.0.1
    • changedInput schema / properties / active / description
      Previous value: -"Whether this gear is actively used"New value: +"False retires the gear (dated today); True un-retires it"
    • addedInput schema / properties / athlete_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Athlete ID (for coaches managing multiple athletes)"
+}
    • removedInput schema / properties / brand
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Updated brand"
-}
    • changedInput schema / properties / gear_type / description
      Previous value: -"Updated type (BIKE, SHOE, TRAINER, etc.)"New value: +"Updated type, case-insensitive (Bike, Shoes, Trainer, Chain, ...)"
    • removedInput schema / properties / model
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Updated model"
-}
    • removedInput schema / properties / primary
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Whether this is the primary gear of this type"
-}
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one genuine behavioral fact beyond that — PATCH-style partial update semantics ("Only fields you pass are sent") — but says nothing about error behavior for unknown gear_id, permission requirements, or the retire/un-retire side effect of active=false.

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 short sentences, zero filler, with the action stated first and the partial-update caveat immediately after. Nothing could be trimmed without losing information.

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

Completeness3/5

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

With full schema coverage, an output schema, and annotations carrying the safety profile, the definition is callable as written. However, for a mutation tool it omits notable context an agent would want: what happens if gear_id does not exist or belongs to another athlete, and that setting active=false permanently dates a retirement.

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 every parameter (including the nuanced active=false retirement behavior and coach-oriented athlete_id) is already documented. The description's partial-update note reinforces optionality but adds no field-level detail beyond the schema. Baseline 3 applies.

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?

"Update an existing gear item" gives a specific verb (update) and resource (gear item), which cleanly separates it from icu_create_gear, icu_delete_gear, and icu_update_gear_reminder. It does not explicitly name or differentiate against any sibling, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never states when to use this tool versus alternatives such as icu_create_gear (new item) or icu_update_gear_reminder (reminders). Usage is only implied by the verb "update" and the required gear_id.

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