Skip to main content
Glama
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

icu_update_gear

Idempotent

Update an existing gear item by sending only the fields you need to change. Rename, retype, retire, or unretire gear in Intervals.icu without overwriting other data.

Instructions

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

Input Schema

TableJSON 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

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: +"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

A3.5/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnly=false, idempotent=true, destructive=false). The description adds one genuinely useful behavioral fact beyond them: fields not passed are left untouched, which is what makes the null-defaulted optional parameters safe. It says nothing about permissions, failure modes, or what happens on an unknown gear_id.

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 padding, with the core action front-loaded and the update-semantics caveat immediately after.

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?

For a mutation tool with annotations covering safety and an output schema covering returns, the description supplies the one thing an agent most needs to call it correctly: the partial-update contract. Only edge-case behavior (invalid gear_id, cross-athlete access for coaches) is unaddressed.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, and the description earns above baseline by clarifying the partial-update contract — omitted/null fields are not sent, so the agent knows it should not pass nulls to clear values. It still does not explain the retire/un-retire semantics of 'active' (that lives in the schema).

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?

The description gives a specific verb+resource ('Update an existing gear item'), making the operation unambiguous and distinguishable by name from icu_create_gear and icu_delete_gear. It does not, however, explicitly contrast itself with those siblings inside the description text.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as create_gear or delete_gear. The second sentence is behavioral (partial-update semantics), not usage routing.

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