Skip to main content
Glama
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

icu_update_sport_settings

Idempotent

Update a sport's threshold record, including outdoor/indoor FTP, FTHR, pace, or swim threshold, by sport ID; optionally recalculate HR zones.

Instructions

Update an existing per-sport threshold record (outdoor/indoor FTP, FTHR, pace, swim).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ftpNoFunctional Threshold Power in watts (for cycling)
fthrNoFunctional Threshold Heart Rate in bpm
sport_idYesID of the sport settings to update
athlete_idNoAthlete ID (for coaches managing multiple athletes)
indoor_ftpNoIndoor Functional Threshold Power in watts (for cycling)
pace_thresholdNoThreshold pace in min/km (e.g., 4.5 for 4:30/km)
swim_thresholdNoSwim threshold in min/100m (e.g., 1.5 for 1:30/100m)
recalc_hr_zonesNoRecalculate HR zones from the updated threshold heart rate

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. Changed2 schema fields changedv4.2.0
    • addedInput schema / properties / indoor_ftp
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Indoor Functional Threshold Power in watts (for cycling)"
+}
    • addedInput schema / properties / recalc_hr_zones
      Added value: +{
+  "default": true,
+  "description": "Recalculate HR zones from the updated threshold heart rate",
+  "type": "boolean"
+}
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a mutating (readOnlyHint=false) but idempotent and non-destructive operation, so the safety profile is covered. The description adds that it operates on a threshold record and which thresholds are affected, but omits useful behavioral context such as partial-update semantics (only supplied fields change) and the auto-recalculation side effect implied by recalc_hr_zones defaulting to true.

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 that names the action, the resource, and the field domain with no wasted words.

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 described, and annotations cover the safety profile, leaving the description only to frame the operation, which it does. It would be fully complete with a note on partial-update behavior and the HR-zone recalculation default, but the essentials for a correct call are present.

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 coverage is 100% with per-parameter descriptions that already document each threshold type, unit, and the sport_id/athlete_id roles. The description's field list largely restates the schema, adding no unit or format detail beyond it, so 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 ('Update') and resource ('an existing per-sport threshold record'), and enumerates the domain fields (outdoor/indoor FTP, FTHR, pace, swim). 'Existing' implicitly distinguishes it from create_sport_settings, but it never names the sibling explicitly, so the differentiation is inferable rather than stated.

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 word 'existing' implies the record must already be present and that this is a modify-not-create operation, which gives implied usage guidance. However, it does not explicitly say when to use this vs icu_create_sport_settings or icu_apply_sport_settings, nor mention prerequisites such as needing the sport_id first.

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