Skip to main content
Glama
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

icu_get_power_curves

Read-onlyIdempotent

Fetch the power-vs-duration curve for best sustained watts from 5s to 1h over a chosen window. Use for FTP estimation and peak-power tracking.

Instructions

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

Use for FTP estimation, peak-power tracking, strengths/weaknesses across duration profiles. For time-in-zone distribution within a single activity, use icu_get_power_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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful behavioral context beyond them: what the curve aggregates (highest sustained watts per duration) and the 5s-to-1h range. It does not discuss auth scope or how the aggregation window interacts with parameters, so not a full 5.

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?

Two compact sentences plus a routing clause; the core definition is front-loaded and every clause carries information. No filler.

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?

With an output schema present, return format needn't be explained, and rich annotations carry the safety profile. The description covers what the tool computes, when to use it, and which sibling to use instead — sufficient for correct selection and 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. The description's reference to the 'chosen window' loosely maps to days_back/time_period but adds no syntax, format, or interaction detail beyond the schema. Baseline 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 (fetch) and resource (power-vs-duration curve), then defines it precisely: best sustained watts across durations from 5s to 1h, aggregated over the chosen window. It explicitly names the sibling icu_get_power_histogram as the different tool, so an agent can distinguish them without opening either 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 concrete use cases (FTP estimation, peak-power tracking, strengths/weaknesses across duration profiles) and an explicit when-not/alternative: time-in-zone distribution belongs to icu_get_power_histogram. 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