Skip to main content
Glama
Sign In
intervals.mcp

intervals.mcp

by ryansheppard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_activity_detail

Retrieve comprehensive activity data including laps and intervals from intervals.icu training logs for detailed performance analysis and workout planning.

Instructions

Get full detail for a single activity including laps and intervals.

Args: activity_id: The activity ID (visible in the intervals.icu URL).

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": {
      "activity_id": "<activity_id>"
    },
    "name": "get_activity_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries full disclosure burden. It adds valuable context that 'full detail' specifically includes 'laps and intervals,' but omits safety characteristics (read-only status), error handling (404 behavior), or rate limiting that annotations would typically cover.

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?

Efficient two-part structure with the main sentence front-loaded with key behavioral details (laps/intervals), followed by a standard Args block. No redundant or wasted text.

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?

Appropriate for a single-parameter tool without output schema. The description conceptually explains the return value (laps/intervals) and documents the required parameter. Minor gap regarding error cases or authentication, but sufficient for the complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, requiring description compensation. The Args section adds critical context beyond the schema: it defines activity_id and specifies it is 'visible in the intervals.icu URL,' helping users locate the correct value. Could be a 5 if it added format validation rules.

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?

Description clearly states the tool 'Get[s] full detail for a single activity' with specific scope including 'laps and intervals.' The 'single activity' focus effectively distinguishes it from sibling get_activities (likely a list operation).

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?

No explicit when-to-use guidance or comparison to alternatives (e.g., 'Use this instead of get_activities when you need lap data'). However, the 'single activity' phrasing implies usage for detailed retrieval versus bulk listing.

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