Skip to main content
Glama
hhopke
by hhopke

icu_get_activity_streams

Read-onlyIdempotent

Fetch second-by-second activity streams—power, heart rate, cadence, GPS, altitude—for charting or custom signal analysis; request raw_heartrate for uncorrected max HR.

Instructions

Fetch RAW per-sample time-series of one activity — second-by-second arrays for power, HR, cadence, speed, altitude, GPS, temperature, grade, etc.

Heavy payload. Use only when you need the underlying signal for visualization or custom analysis. Most "how was my ride?" questions are better answered by get_activity_details (summary metrics) or get_activity_intervals (per-lap breakdown).

Stream-type filter accepts any of: watts, heartrate, cadence, velocity_smooth, altitude, distance, time, latlng, temp, moving, grade_smooth, raw_heartrate, fixed_heartrate.

heartrate is CORRECTED data: Intervals.icu replaces readings above the athlete's configured max HR with an interpolated line at import, so it can never exceed that setting. raw_heartrate is the uncorrected trace and is the only way to see a genuine new max that was clipped away — the platform never raises the setting on its own. Request it explicitly; it is not in the default set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
streamsNoList of stream types (e.g., ['watts', 'heartrate', 'cadence']). If not specified, the activity's default streams are fetched — which does NOT include raw_heartrate or fixed_heartrate; ask for those by name.
activity_idYesActivity ID to fetch streams for

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • changedInput schema / properties / streams / description
      Previous value: -"List of stream types (e.g., ['watts', 'heartrate', 'cadence']). If not specified, all streams are fetched."New value: +"List of stream types (e.g., ['watts', 'heartrate', 'cadence']). If not specified, the activity's default streams are fetched — which does NOT include raw_heartrate or fixed_heartrate; ask for those by name."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/destructive flags, but the description adds substantial non-obvious behavior: payload heaviness warning, and the crucial heartrate-vs-raw_heartrate semantic — that heartrate is pre-corrected and capped at max HR while raw_heartrate exposes the clipped peak. This corrects a real misinterpretation risk.

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 core purpose, then usage routing, then filter values, then the important heartrate nuance. Dense but every paragraph earns its place; the multi-paragraph layout could be slightly tighter but nothing is wasted.

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?

Output schema exists so return shape needn't be explained. Given the tool's complexity, the description covers what it returns, when to choose it vs siblings, valid filters, and the subtle raw_heartrate caveat — nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents both params, so baseline is 3. The description goes beyond by enumerating the accepted stream-type values (including ones the schema does not list) and warning that the default set excludes raw_heartrate/fixed_heartrate — real added semantics.

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?

Specific verb ('Fetch') plus resource ('RAW per-sample time-series') with an explicit enumeration of what streams are returned. It clearly distinguishes itself from sibling summary tools (get_activity_details, get_activity_intervals) and from the mutation sibling (update_activity_streams).

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?

Explicit when-to-use ('visualization or custom analysis') and when-not ('Most "how was my ride?" questions are better answered by get_activity_details or get_activity_intervals'), naming the specific alternatives. This is exactly the routing guidance an agent needs.

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