Intervals.icu MCP Server

Create calendar event

create_event

Add a planned workout, race, note or other event to an athlete's Intervals.icu training calendar by specifying start date and category.

Instructions

Create an event on the athlete's training calendar (planned workout, race, note, etc.).

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": {
      "start_date_local": "<start_date_local>",
      "category": "<category>"
    },
    "name": "create_event"
  }
}

Input Schema

Name	Required	Description
`name`	No	Event name/title
`type`	No	Sport type e.g. Ride, Run, Swim, WeightTraining
`category`	Yes	Event category
`distance`	No	Planned distance in meters
`description`	No	Event notes or description
`moving_time`	No	Planned duration in seconds
`start_date_local`	Yes	Start date/time in ISO 8601 format e.g. 2024-06-01T08:00:00

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 16, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, open-world write, so the safety profile is covered externally. The description adds only that the target is the athlete's training calendar; it does not say whether duplicate events are allowed, what permissions are required, or what happens on a date collision.

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?

A single front-loaded sentence with the verb and resource first and the clarifying examples after. Nothing is padded and nothing needs to be re-read.

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?

For a 7-parameter mutation with no output schema, the description is thin: it says nothing about the created object's return shape, error behavior, or whether category choices alter required fields. Annotations cover the safety side, but the description leaves a real gap around mutation outcomes.

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 every parameter (category enum, ISO date pattern, distance/duration units) is already documented in the schema. The description contributes no additional parameter meaning, which is the expected baseline when the schema does the heavy lifting.

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 ('Create') and resource ('event on the athlete's training calendar'), with parenthetical examples (planned workout, race, note) that make the intent unambiguous. It implicitly separates itself from read-side siblings like get_event/list_events, though it never names them explicitly.

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, no mention of prerequisites, and no routing between this and siblings such as update/delete or bulk list operations. The parenthetical gives event kinds but not the conditions under which an agent should call this tool.

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