Skip to main content
Glama
Sign In
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Create Sport Settings

icu_create_sport_settings

Create per-sport threshold settings for cycling, running, or swimming, including outdoor and indoor FTP, FTHR, pace, and swim thresholds.

Instructions

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

Input 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

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the write profile is covered. The description adds only the field groupings (outdoor vs indoor FTP), and stays silent on the meaningful behavioral question for a non-idempotent create: whether a duplicate sport_type is rejected or replaces the existing thresholds.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the resource and the key qualifier (per-sport) come first. It is efficient, though the trailing field list largely duplicates the schema property names.

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?

With an output schema present, return values need not be explained. However, for a non-idempotent mutation with an optional coach-scoped athlete_id, the description omits duplicate-handling behavior and any permission/scope prerequisites, leaving an agent to infer them from annotations alone.

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%, with each parameter carrying its own unit-bearing description (watts, bpm, min/km, min/100m). The description merely restates those field names, adding no unit, format, or defaulting semantics beyond 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?

States a specific verb and resource ("Create a per-sport threshold record") and enumerates the metric families covered (FTP, FTHR, pace, swim). The 'create' verb implicitly separates it from the sibling icu_get_sport_settings and icu_update_sport_settings, though neither is named explicitly.

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 guidance on when to create versus when to use icu_update_sport_settings, nor any note about what happens if a record already exists for the given sport_type. The athlete_id parameter's coaching use case is only explained in the schema, not in the description.

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