Intervals.icu MCP Server

get_activity_best_efforts

Retrieve peak values over specified time or distance windows for an activity's data streams like watts, heart rate, or pace to analyze performance efforts.

Instructions

Get the best efforts (peak values over windows) for an activity.

Args:
    activity_id: The Intervals.icu activity ID.
    stream: Data stream to analyze — e.g. "watts", "heartrate", "pace" (default "watts").
    duration: Optional window duration in seconds to target.
    distance: Optional window distance in meters to target.
    count: Optional maximum number of efforts to return.

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_best_efforts"
  }
}

Input Schema

Name	Required	Default
`count`	No
`stream`	No	watts
`distance`	No
`duration`	No
`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.3/5.0

Behavior3/5

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

No annotations are supplied, but 'Get' clearly signals a read-only operation with no side effects. The description explains the analytical concept (peak values over windows) but says nothing about permissions, cost, or how duration and distance interact, leaving some behavioral gaps.

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 one-line summary is front-loaded and the Args block is compact and scannable. Some parameter text duplicates schema field names, but it earns its place given zero schema coverage.

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 values need not be described. However, for a 5-parameter analytical tool, the definition omits the duration/distance interaction and the set of valid stream identifiers, which an agent would need to invoke it confidently.

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?

With 0% schema description coverage, the Args block carries all parameter meaning: it gives units (seconds, meters), a default ('watts'), example stream values ('heartrate', 'pace'), and the intent of count. It does not explain whether duration and distance are mutually exclusive or which takes precedence.

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?

The opening sentence names a specific verb ('Get') and resource ('best efforts') and clarifies the domain term with a parenthetical definition ('peak values over windows'). It is clear what the tool returns, though it does not distinguish itself from siblings like get_activity_intervals or get_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 Guidelines2/5

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

There is no guidance on when to choose this tool over the many related activity tools (intervals, streams, details), nor on when to use duration versus distance windows. Usage is only implied by the parameter list, leaving routing decisions to the agent.

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