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

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Get Hr Curves

icu_get_hr_curves
Read-onlyIdempotent

Fetch the heart-rate-vs-duration curve showing best sustained HR from 5 seconds to 1 hour across a chosen window, so you can track cardiovascular-fitness trends.

Instructions

Fetch the HR-vs-duration curve — best (highest) sustained HR across durations from 5s up to 1h, aggregated over the chosen window.

Use for cardiovascular-fitness trends. For the athlete's HR zones and max HR, call icu_get_sport_settings — this tool does not return zone bands, and its peak_hr_bpm is the top of this curve, which Intervals.icu has already clipped to the configured max HR at import. For time-in-zone distribution within a single activity, use get_hr_histogram instead.

Input Schema

NameRequiredDescriptionDefault
days_backNoNumber of days to analyze (optional)
athlete_idNoAthlete ID (for coaches managing multiple athletes)
sport_typeNoSport type (e.g., Ride, Run, Swim, VirtualRide)Ride
time_periodNoTime period shorthand: 'week', 'month', 'year', 'all' (optional)

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

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description still adds genuine value by disclosing that peak_hr_bpm is the curve's top and has been clipped to configured max HR at import, plus that zone bands are NOT returned. It stops short of describing pagination, aggregation mechanics across the window, or how multiple activities are combined.

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?

Three sentences, front-loaded with what the tool returns, then intended use, then exclusions. Every clause carries information; the em-dash parenthetical defines the curve precisely rather than padding.

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 shape need not be described, and annotations cover safety. The description is complete regarding misuse risks (zones, max HR, histogram confusion). The remaining gap is the days_back vs time_period precedence, which neither description nor schema resolves.

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 the schema already documents all four parameters; baseline is 3. The description only alludes to 'the chosen window' without clarifying how days_back and time_period interact or which takes precedence — the one ambiguity in an otherwise well-covered schema.

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?

States a specific verb and resource — 'Fetch the HR-vs-duration curve — best (highest) sustained HR across durations from 5s up to 1h, aggregated over the chosen window' — with the aggregation scope spelled out. This cleanly separates it from icu_get_power_curves, icu_get_pace_curves and icu_get_hr_histogram without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit intended use ('Use for cardiovascular-fitness trends') and names two alternatives with their selecting conditions: icu_get_sport_settings for HR zones/max HR, and get_hr_histogram for time-in-zone distribution. Nothing is left to inference.

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