Skip to main content
Glama
VictorForV

intervals-mcp

by VictorForV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

intervals_get_raw

Retrieve any Intervals.icu v1 API path directly and return raw data, expanding {athlete} and redacting sensitive fields. Use when dedicated tools cannot answer.

Instructions

Escape hatch: GET any intervals.icu v1 path and return it unshaped.

    Use only when a dedicated tool cannot answer the question, since raw
    payloads are large. path is relative to https://intervals.icu/api/v1,
    for example "athlete/{athlete}/activities"; "{athlete}" expands to the
    configured athlete id. Pass query arguments in params, not in the path.
    This is still read-only.

    Field names are returned as-is, but values that look like credentials
    or personal contact info -- email, API keys, tokens, invitation links
    -- are replaced with "[redacted]" wherever they appear in the payload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
paramsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and performs well: it states this is read-only, returns raw unshaped payloads, warns that raw payloads are large, and discloses redaction of credentials and personal contact information. These are precisely the behavioral traits an agent needs to anticipate before invoking an arbitrary API escape hatch.

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?

Each sentence earns its place: purpose, when to avoid, path construction, query-argument placement, read-only reassurance, and redaction behavior. The most important fact is front-loaded, and the description is compact given the amount of necessary context.

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?

For a deliberately generic tool with no output schema and no annotations, the description covers all the essentials: base URL, path variables, params usage, read-only semantics, payload size expectations, and redaction. An agent has enough guidance to call this tool correctly for an arbitrary path, which is exactly the intent of an escape hatch.

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 description coverage is 0%, but the description compensates by explaining that 'path' is relative to https://intervals.icu/api/v1, gives a concrete example, and resolves the '{athlete}' placeholder to the configured athlete ID. It also clarifies that 'params' is for query arguments, which adds semantic meaning that is entirely absent from the bare schema.

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 this tool performs an arbitrary GET against intervals.icu v1 paths and returns them unshaped, using the specific verb 'GET' and resource 'any intervals.icu v1 path'. It also distinguishes itself from dedicated sibling tools by framing it as a fallback escape hatch, so an agent can tell when this tool applies.

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

Usage Guidelines5/5

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

It explicitly says to use this only when a dedicated tool cannot answer, which directly routes agents away from siblings and toward the right tool. It also gives concrete usage rules with an example path, explains the '{athlete}' expansion, and instructs that query arguments belong in params, not the path.

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

Deploy Server

Other Tools