Intervals.icu MCP Server

get_activity_intervals

Retrieve detailed interval metrics for a specific Intervals.icu activity, including power, heart rate, cadence, speed, and environmental data, to analyze workout segments and grouped intervals.

Instructions

Get interval data for a specific activity from Intervals.icu

This endpoint returns detailed metrics for each interval in an activity, including power, heart rate,
cadence, speed, and environmental data. It also includes grouped intervals if applicable.

Args:
    activity_id: The Intervals.icu activity ID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "activity_id": "<activity_id>"
    },
    "name": "get_activity_intervals"
  }
}

Input Schema

Name	Required	Description	Default
`activity_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 2, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden; it does disclose the payload contents (power, HR, cadence, speed, environmental data, grouped intervals), which is useful context beyond the schema. However, it says nothing about pagination, permissions/authentication needs, or behavior when an activity has no intervals, and 'Get' only weakly signals read-only.

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?

The purpose is front-loaded in the first sentence and the payload summary follows efficiently. The 'Args:' block is somewhat redundant with a one-parameter schema and slightly dilutes the otherwise tight structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 documentation is not strictly needed, yet the description spends its bulk restating return fields while omitting the higher-value information an agent needs: how this differs from sibling interval/stream tools and any preconditions. Adequate for a single-parameter read, but with clear gaps.

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 0% and the single property has only a title, so the description must compensate. The Args block adds the meaningful hint that the value is an Intervals.icu activity ID (not an internal ID), but gives no format or example, leaving it barely above the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get interval data for a specific activity') and names the data source, Intervals.icu. It is distinguishable from generic siblings like get_activity_details or get_activity_streams, though it never explains how it differs from the closely related get_activity_interval_stats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of alternatives, despite the sibling list containing get_activity_interval_stats, get_activity_streams, and get_activity_details that could all plausibly be chosen instead. The agent must infer the selection criteria from tool names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.