intervals-icu-mcp

Overview Schema Source Related Servers Discussions Admin

icu_search_intervals

Read-onlyIdempotent

Search intervals across all athlete activities to track workout progress or find comparable historical sessions. Returns activities with interval summaries.

Instructions

Search intervals ACROSS ALL the athlete's activities (cross-activity).

Different from icu_get_activity_intervals (single-activity). Use to track progress on a workout type ("all my threshold intervals over the last year") or find comparable historical sessions. Returns the activities containing matching intervals, each with an interval_summary like "2x 8m 162w" (reps x duration at target).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of matching activities to return
`athlete_id`	No	Athlete ID (for coaches managing multiple athletes)
`max_duration`	No	Maximum interval duration in seconds
`min_duration`	No	Minimum interval duration in seconds
`interval_type`	No	Interval target type: AUTO, POWER, HR, or PACE (what the interval targeted — not the sport and not a workout-step label)
`max_intensity`	No	Maximum interval intensity in percent of threshold (e.g. 105)
`min_intensity`	No	Minimum interval intensity in percent of threshold (e.g. 80)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv5.0.1Sep 11, 2026

addedInput schema / properties / athlete_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Athlete ID (for coaches managing multiple athletes)"
+}

changedInput schema / properties / interval_type / description

Previous value: -"Type of interval to search for"New value: +"Interval target type: AUTO, POWER, HR, or PACE (what the interval targeted — not the sport and not a workout-step label)"

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results to return"New value: +"Maximum number of matching activities to return"

changedInput schema / properties / max_duration / description

Previous value: -"Maximum duration in seconds"New value: +"Maximum interval duration in seconds"

addedInput schema / properties / max_intensity

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Maximum interval intensity in percent of threshold (e.g. 105)"
+}

changedInput schema / properties / min_duration / description

Previous value: -"Minimum duration in seconds"New value: +"Minimum interval duration in seconds"

addedInput schema / properties / min_intensity

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Minimum interval intensity in percent of threshold (e.g. 80)"
+}

First observedv0.1.0May 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds genuinely new behavioral context by explaining the return shape (activities containing matching intervals) and the interval_summary format '2x 8m 162w'. It stops short of noting pagination or result ordering, keeping it at a 4.

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?

Front-loads the cross-activity scope, then the sibling contrast, then use cases and return format. Four short sentences with essentially no filler, though the return-format sentence could be tighter.

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 annotations, a 100%-covered schema, and an output schema, the description only needs to convey purpose, disambiguation and what comes back — all present, including the interval_summary example that makes the result interpretable.

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 duration, intensity, interval_type and limit are all documented in the schema itself. The description adds no parameter-level meaning (e.g., how min/max intensity interact or how filters combine), so the 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 and resource with explicit scope: 'Search intervals ACROSS ALL the athlete's activities (cross-activity)'. It directly names and contrasts with the sibling icu_get_activity_intervals (single-activity), so an agent can pick correctly 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 the alternative and the condition that selects it, plus two concrete use cases ('all my threshold intervals over the last year', 'find comparable historical sessions'). Nothing about when to use this vs. the single-activity tool 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