Skip to main content
Glama
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

icu_create_gear

Create a new gear item to track equipment usage and maintenance for bikes, shoes, trainers, and more. Specify name and gear type, with optional active status and athlete ID.

Instructions

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

Input Schema

TableJSON 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

TableJSON 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
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds no behavioral context beyond that: it says nothing about duplicate names (relevant given idempotentHint=false), permission requirements, or whether the new gear is auto-assigned to activities.

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, resource second, and domain examples last. No filler, no repetition of schema or annotation content.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile; the description covers purpose adequately for a 4-parameter create tool. The only real gap is the absence of any note on duplicate handling or the coach/athlete_id scenario.

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 name, active, gear_type and athlete_id are all documented in the schema itself, including the gear_type vocabulary list. The description adds no parameter-level meaning beyond that, making the baseline 3 appropriate.

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 clarifies the domain with concrete examples (bikes, shoes, trainers). It is distinguishable from icu_update_gear, icu_delete_gear and icu_get_gear_list by the verb, though it does not explicitly call out the near-neighbor 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 Guidelines3/5

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

The phrase 'for tracking equipment usage and maintenance' implies why an agent would create gear, but there is no explicit when-to-use statement, no prerequisite (e.g. athlete_id for coaches), and no named alternatives. Usage is inferable rather than stated.

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