Intervals.icu MCP Server

get_sport_settings

Retrieve an athlete's per-sport training settings—FTP, zones, and thresholds—used for load, intensity, and zone calculations. Filter by sport or omit it to return all sports.

Instructions

Get the athlete's per-sport training settings (FTP, zones, thresholds).

These are the values that drive load, intensity and zone calculations across
Intervals.icu. Each record's "Settings ID" is the identifier update_sport_settings
uses to target a specific sport.

Args:
    sport: Optional sport type to filter by (e.g. "Ride", "Run"). Matches the
        record's sport types case-insensitively. If omitted, all sports are returned.

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_sport_settings"
  }
}

Input Schema

Name	Required	Description	Default
`sport`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose that this is a read operation ("Get"), what the records contain, and the important cross-tool detail that each record's Settings ID is the handle update_sport_settings targets. It doesn't mention authentication/athlete scoping or rate limits, leaving a modest gap.

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

Conciseness4/5

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

The core purpose and the sibling relationship are front-loaded in the first sentence, and the Args block is clean and scannable. The middle sentence about load/intensity/zone calculations is mildly decorative rather than operational, which keeps it from a 5.

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?

With one optional parameter, no annotations, and an output schema that already defines return shape, the description covers everything an agent needs: what it returns, how to filter, and how the returned ID feeds update_sport_settings. No material gap remains.

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?

Schema coverage is 0%, so the description must fully carry the single parameter, and it does: it is optional, matches sport types case-insensitively, gives example values ("Ride", "Run"), and states the default behavior when omitted (all sports returned). Nothing about the parameter is left ambiguous.

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?

States a specific verb and resource ("Get the athlete's per-sport training settings") and immediately enumerates the concrete fields returned (FTP, zones, thresholds). It also distinguishes itself from the sibling mutator update_sport_settings by timing: this is the read that produces the Settings ID the update tool consumes.

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?

It gives clear context: call without arguments to get all sports, or pass a sport to narrow results. The relationship to update_sport_settings is spelled out, so an agent knows this is the read half of the read/update pair. There is no explicit "don't use this for X" exclusion, which keeps it below a 5.

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