Skip to main content
Glama
Sign In
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Create Gear

icu_create_gear

Create a new gear item for tracking equipment usage and maintenance, including bikes, shoes, and trainers, with optional active status and athlete assignment.

Instructions

Create a new gear item for tracking equipment usage and maintenance (bikes, shoes, trainers, etc.).

Input Schema

NameRequiredDescriptionDefault
nameYesName of the gear item
activeNoWhether this gear is actively used (False = retired)
gear_typeYesGear type, case-insensitive. Whole items: Bike, Shoes, Wetsuit, Trainer, RowingMachine, Skis, Snowboard, Boat, Board, Equipment, Accessories, Apparel, Computer. Components: Chain, Cassette, Wheel, Tyre, Frame, Pedals, PowerMeter, and more.
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: +"Whether this gear is actively used (False = retired)"
    • 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": "Brand name"
-}
    • changedInput schema / properties / gear_type / description
      Previous value: -"Type of gear (e.g., 'BIKE', 'SHOE', 'TRAINER', 'WETSUIT', 'OTHER')"New value: +"Gear type, case-insensitive. Whole items: Bike, Shoes, Wetsuit, Trainer, RowingMachine, Skis, Snowboard, Boat, Board, Equipment, Accessories, Apparel, Computer. Components: Chain, Cassette, Wheel, Tyre, Frame, Pedals, PowerMeter, and more."
    • removedInput schema / properties / model
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Model name"
-}
    • removedInput schema / properties / primary
      Removed value: -{
-  "default": false,
-  "description": "Whether this is the primary gear of this type",
-  "type": "boolean"
-}
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the write, non-destructive, non-idempotent, open-world profile, so the safety bar is low. The description adds the domain framing (equipment usage/maintenance) but says nothing about duplicate handling given idempotentHint=false, or what happens when a gear name already exists.

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?

A single front-loaded sentence with the verb first and examples that earn their place by clarifying what 'gear' covers. Nothing redundant.

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?

With full schema coverage, annotations, and an output schema, the return value and safety semantics are already covered, so the description is nearly sufficient. The only real gap is the absence of usage guidance for a mutation tool in a large sibling set.

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%, including the lengthy gear_type enumeration and the coach-oriented athlete_id note, so the schema carries all parameter meaning. The description adds no parameter-level detail and the baseline of 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?

States a specific verb and resource ('Create a new gear item') and adds the domain purpose ('tracking equipment usage and maintenance') with concrete examples. It is distinguishable from the sibling create/read/update/delete gear tools by the verb alone, though it never names them.

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?

No when-to-use guidance, no prerequisites (e.g., whether gear must be attached to an athlete, coach vs. self), and no exclusions. Only a generic purpose phrase implies usage; the agent must infer everything else.

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