Skip to main content
Glama
B3r3z

Intervals.icu MCP Server

by B3r3z

get_activities

List activities within a date range with paginated requests, optionally filtered by sport, from Intervals.icu.

Instructions

List activities in a half-open local-date range with bounded paging.

start_date is inclusive and end_date_exclusive is exclusive. A valid empty list is different from a malformed upstream response. The first page is snapshotted for cursor continuation, and a cursor is valid only for the same athlete, range, timezone, and sport filter. The source endpoint does not expose a trustworthy completeness marker, so source completeness stays null even when the returned list is short. A Hidden source stub without a sport field is retained for identity, but a requested sport match is reported as unverified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
sportsNo
api_keyNo
timezoneNoEurope/Warsaw
page_sizeNo
athlete_idNo
start_dateNo
end_date_exclusiveNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
errorNo
queryNo
sourceYes
statusYes
coverageYes
warningsNo
paginationNo
request_idNo
schema_versionNo1.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full disclosure burden and does so thoroughly: it documents inclusive/exclusive date semantics, empty vs malformed responses, cursor snapshotting, cursor validity constraints, null completeness, and hidden source stub behavior. This is exceptional behavioral transparency.

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 dense but every sentence earns its place, covering only substantive behavioral details. The main purpose is front-loaded, followed by targeted clarifications, with no repetition of schema-provided defaults.

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?

The description is remarkably complete for a tool with no annotations, addressing pagination, cursors, completeness, and edge-case response behavior. It leaves some parameter semantics unexplained, but the presence of an output schema reduces the need to describe return values, and the core call semantics are well covered.

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 0%, so the description must compensate; it does add real meaning for start_date and end_date_exclusive (inclusive/exclusive) and cursor (validity constraints). However, several parameters such as limit, page_size, sports, timezone, and athlete_id are left to their schema names/defaults with no added semantics.

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 opens with the specific verb 'List activities' and the resource, and immediately scopes it to a 'half-open local-date range with bounded paging.' This clearly separates it from sibling activity-level tools like get_activity_details or get_activity_streams, despite not naming them.

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?

The description makes the list/query context clear, but it does not explicitly state when to choose this tool over alternatives like get_activity_details or get_events, nor does it mention exclusions. It provides clear usage context but no explicit routing guidance.

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