Intervals.icu MCP Server

get_workout

Retrieve a single library workout's full structure, including steps and targets, by workout ID.

Instructions

Get a single library workout's full structure (steps and targets).

Args:
    workout_id: The Intervals.icu workout 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": {
      "workout_id": "<workout_id>"
    },
    "name": "get_workout"
  }
}

Input Schema

Name	Required	Description	Default
`workout_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

A4.2/5.0

Behavior3/5

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

With no annotations provided, the description must clarify that this is a read-only operation, which it implicitly does by using the verb 'Get.' It is adequate but lacks explicit context on authentication needs or potential rate limits.

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?

The description is well-structured with a clear summary followed by an indented argument list. Every sentence is highly functional and concise.

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?

Given it is a simple read-only lookup with one parameter, the definition provides all necessary context. The parameter is uniquely identified by its source system (Interval scores.icu), making it complete.

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

Parameters5/5

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

Since the schema description coverage is 0%, the description adds critical value by defining 'workout_id' as 'The Intervals.icu workout ID,' providing necessary domain context for the agent.

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?

The description clearly states the action ('Get'), the resource ('a single library workout'), and the scope ('full structure'). This clearly distinguishes it from general activity retrieval tools like get_activities.

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?

While it implies its use for predefined library workouts, it does not explicitly guide the agent on when to choose this over other methods (e.g., if it's better than get_custom_item_by_id for predefined sets).

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