Skip to main content
Glama
Sign In
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Search Intervals

icu_search_intervals
Read-onlyIdempotent

Search intervals across all athlete activities to track progress by workout type or find comparable historical sessions. Returns matching 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

NameRequiredDescriptionDefault
limitNoMaximum number of matching activities to return
athlete_idNoAthlete ID (for coaches managing multiple athletes)
max_durationNoMaximum interval duration in seconds
min_durationNoMinimum interval duration in seconds
interval_typeNoInterval target type: AUTO, POWER, HR, or PACE (what the interval targeted — not the sport and not a workout-step label)
max_intensityNoMaximum interval intensity in percent of threshold (e.g. 105)
min_intensityNoMinimum interval intensity in percent of threshold (e.g. 80)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields 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)"
+}
    • 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)"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: results are activities (not raw intervals) and each carries an interval_summary rendered as '2x 8m 162w' (reps x duration at target). It does not mention result ordering or paging beyond the limit param, so not a 5.

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-loaded with the cross-activity scope, then the sibling contrast, then usage and return shape — every clause maps to a decision the agent must make. The return-format example is slightly redundant given an output schema exists, keeping it just short of 5.

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 7 all-optional, fully documented params, annotations covering safety, and an output schema, the description supplies exactly the missing pieces: cross-activity scope, the exclusion versus the single-activity sibling, and the shape of the returned interval_summary. Nothing an agent needs to call it correctly is absent.

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% and the schema itself carries strong semantics, including the note that interval_type means AUTO/POWER/HR/PACE and is neither the sport nor a workout-step label. The description adds no parameter-level detail (e.g. that intensity is relative to threshold, or how athlete_id defaults), 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 (search intervals) plus an explicit scope (across ALL the athlete's activities, cross-activity) and names the sibling it differs from (icu_get_activity_intervals, single-activity). An agent can distinguish the two 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 (tracking progress on a workout type, e.g. 'all my threshold intervals over the last year', finding comparable historical sessions) and an explicit alternative with the condition that selects it. Nothing is left to inference about when to pick this over the single-activity tool.

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