Intervals.icu MCP Server

get_workouts

List and filter the athlete's reusable workout library by folder or sport type to quickly find workouts for planning or assignment.

Instructions

List the athlete's reusable workout library.

Filtering is applied client-side (the API returns the full library).

Args:
    folder_id: Optional folder ID to restrict results to one folder.
    sport_type: Optional sport type to filter by (e.g. "Ride", "Run").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_workouts"
  }
}

Input Schema

Name	Required	Description	Default
`folder_id`	No
`sport_type`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and delivers a genuinely non-obvious behavioral fact: filtering happens client-side and the API always returns the full library, which affects payload size and latency expectations. "List" also implicitly signals a read-only operation. It doesn't address auth, pagination, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short blocks — purpose, a behavioral caveat, then per-argument notes — front-loaded with the most important sentence first. Nothing is repeated from structured fields and there is no filler.

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

Completeness4/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 needn't be described, and the description covers purpose, filtering semantics, and both parameters. The only real gap is the relationship to get_workout, which matters given how similarly named that sibling is.

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 description coverage is 0%, so the description must compensate and it does: both parameters are explained, and sport_type gains concrete example values ("Ride", "Run") that substitute for the missing enum. folder_id's origin (where folder IDs come from) is still unexplained.

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 description states a specific verb and resource ("List the athlete's reusable workout library"), which is clearly distinct from activity-listing siblings like get_activities. It stops short of naming the closest sibling (get_workout) so the library-vs-single-workout boundary is left implicit.

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

Usage Guidelines3/5

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

Usage is only implied by the purpose statement — an agent can infer this is the bulk listing call for saved workout templates. There is no explicit when-to-use/when-not guidance and no routing to get_workout for retrieving a single workout by ID.

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