Skip to main content
Glama
Sign In
intervals-icu-mcp

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Get Sport Settings

icu_get_sport_settings
Read-onlyIdempotent

Retrieves per-sport thresholds and configured power, heart rate, and pace zones for an athlete, providing the exact zone data used for time-in-zone, HRSS, and TSS calculations.

Instructions

Get per-sport thresholds and the athlete's configured power/HR/pace zones.

Returns outdoor/indoor FTP, FTHR, max HR, running pace and swim threshold, plus the zone sets configured in Intervals.icu (HR zones in bpm, power zones as %FTP, pace zones as % of threshold pace) with their names.

This is the ONLY source of the athlete's real zones. Intervals.icu derives them from the threshold (unless set explicitly) and stamps them into every activity at import, so time-in-zone, HRSS and TSS are all computed from these — reasoning about zones from any other number puts the answer at odds with the athlete's own charts. Zones are not derived from curve data.

Input Schema

NameRequiredDescriptionDefault
athlete_idNoAthlete ID (for coaches managing multiple athletes)

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. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavioral context: zones are derived from thresholds unless set explicitly, are stamped into activities at import, and drive time-in-zone, HRSS, and TSS calculations. This gives the agent crucial domain context for interpreting and trusting the returned zones.

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?

The description is front-loaded with purpose, then details outputs and behavioral significance. It is mostly efficient, though the repeated emphasis on 'real zones' and the final warning add slight verbosity for a simple getter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema and read-only annotations, the description provides ample context: what is returned, why the zones matter, and how they relate to downstream metrics. An agent has enough information to call and interpret the tool correctly.

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?

The schema has 100% description coverage and the single athlete_id parameter is already documented there, including its purpose for coaches. The description adds no additional parameter meaning, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: get per-sport thresholds and configured power/HR/pace zones. It further specifies the included fields (FTP, FTHR, max HR, pace, swim threshold) and zone sets, making the tool's scope unambiguous against sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It strongly indicates when this tool is the right source: 'This is the ONLY source of the athlete's real zones,' and warns that reasoning from other numbers conflicts with the athlete's charts. It implicitly distinguishes itself from curve-based siblings by stating zones are not derived from curve data, though it does not explicitly name alternatives or exclusions.

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