Skip to main content
Glama
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

icu_create_sport_settings

Set per-sport threshold records including FTP, indoor FTP, FTHR, pace, or swim threshold so training zones reflect your current fitness for cycling, running, or swimming.

Instructions

Create a per-sport threshold record with outdoor/indoor FTP, FTHR, pace, or swim settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ftpNoFunctional Threshold Power in watts (for cycling)
fthrNoFunctional Threshold Heart Rate in bpm
athlete_idNoAthlete ID (for coaches managing multiple athletes)
indoor_ftpNoIndoor Functional Threshold Power in watts (for cycling)
sport_typeYesType of sport (e.g., 'Ride', 'Run', 'Swim')
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)

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. Changed1 schema field 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)"
+}
  3. 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 this as a non-read-only, open-world, non-idempotent, non-destructive write. The description adds that the record is per-sport and enumerates the threshold families, but says nothing about duplicate handling, authorisation, or what happens to existing records. With annotations covering the safety profile, this is a modest but real addition.

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 a clear verb and a compact enumeration of the covered metrics. No filler, no redundancy.

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?

An output schema exists, so return values need not be described. However, as a mutation on a resource that also has get/update/apply siblings, the absence of usage routing and mutation semantics leaves the definition only minimally complete.

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 one of the 7 parameters is already documented in the schema with useful detail (units, examples, coach context). The description only echoes the metric families and adds no format or constraint information beyond what the schema provides. 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?

The description states a specific verb (Create) and resource (per-sport threshold record) and enumerates the covered metric families (outdoor/indoor FTP, FTHR, pace, swim). It does not name the sibling tools or explain how it differs from create_sport_settings, get_sport_settings, or update_sport_settings, so it stops short of 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?

There is no when-to-use guidance, no indication of when to choose create vs update_sport_settings or apply_sport_settings, and no prerequisites. The agent is left to infer usage from the name alone.

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