Intervals.icu MCP Server

List calendar events

list_events

Read-onlyIdempotent

List planned workouts, races, notes, holidays, sickness, and injuries from the training calendar. Use it to review upcoming plans or compare them with completed activities.

Instructions

List calendar entries: planned workouts (with the workout steps as text), races, notes, holidays, sickness and injuries. Defaults to today and the next 2 weeks. Use it to see what is planned or to compare the plan with completed activities.

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": "list_events"
  }
}

Input Schema

Name	Required	Description
`newest`	No	Last day (YYYY-MM-DD), inclusive. Default: oldest + 13 days.
`oldest`	No	First day (YYYY-MM-DD). Default: today.
`categories`	No	Only these categories, e.g. ["WORKOUT"] or ["RACE_A","RACE_B","RACE_C"].
`include_descriptions`	No	Include workout text and notes (default true).

Output Schema

Name	Required	Description	Default
`count`	Yes
`range`	Yes
`events`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Sep 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds valuable behavioral context: the default date range (today and next 2 weeks) and that workout steps are included as text, which is beyond what annotations provide. No contradictions detected.

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 two sentences with no fluff. The primary purpose is front-loaded, followed by content types, default range, and usage. Every sentence earns its place and the structure is efficient and easy to parse.

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?

For a read-only list tool with an output schema and rich annotations, the description covers the essential context: what it lists, the default time window, and a suggested use case. It does not explain return structure (covered by output schema) or parameter details (covered by schema). The only minor gap is explicit guidance on alternative tools, but that is handled in usage guidelines.

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 100%, so the schema already documents all four parameters including defaults for oldest and newest. The description adds minimal extra meaning, only hinting at include_descriptions via 'workout steps as text.' This meets the baseline 3 for high schema coverage; the description does not meaningfully compensate for any gaps.

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 tool lists calendar entries and enumerates the specific types (workouts, races, notes, holidays, sickness, injuries), making the resource and scope unambiguous. It also implies a distinction from activity listing by focusing on planned vs. completed activities, helping an agent differentiate it from list_activities.

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

Usage Guidelines4/5

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

The description gives a clear context: 'Use it to see what is planned or to compare the plan with completed activities.' This tells the agent when to use it, but it does not explicitly name alternatives or exclusion conditions, such as 'use list_activities for completed activities' or 'use get_event for a single event.' Thus it stops short of full explicitness.

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