Skip to main content
Glama
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

icu_get_hr_curves

Read-onlyIdempotent

Retrieve the highest sustained heart rate across durations from 5 seconds to 1 hour over a chosen window, revealing cardiovascular fitness trends over time.

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

TableJSON 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

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

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the safe read-only, idempotent profile. The description adds genuine behavior beyond them, notably that peak_hr_bpm is the top of the curve and has already been clipped to the configured max HR at import, plus that it does not return zone bands. This is useful nuance, though return structure and aggregation mechanics are left to the output schema.

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?

Front-loads the core definition, then segments usage and disambiguation into tight sentences with zero filler. Every sentence carries either scope, routing, or behavioral information.

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?

An output schema exists, so return-value explanation is unnecessary. Combined with the routing guidance and the behavioral note about max-HR clipping, the description is complete for correct invocation.

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 all four parameters (days_back, athlete_id, sport_type, time_period) are already documented in the schema. The description references the 'chosen window' but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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') and defines exactly what the curve contains: best sustained HR across durations from 5s to 1h, aggregated over the window. It also distinguishes itself from icu_get_sport_settings and get_hr_histogram by name.

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 explicit intended use ('Use for cardiovascular-fitness trends') and names two alternatives with the conditions that select them: sport_settings for HR zones/max HR, hr_histogram for time-in-zone distribution within a single activity.

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