Skip to main content
Glama
Sign In
Intervals MCP

Intervals MCP

by bradyap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

activity_get

Read-onlyIdempotent

Retrieve a specific Intervals activity by ID. Optionally include detected intervals to analyze cycling training data.

Instructions

Get one Intervals activity by ID.

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": {
      "activityId": "<activityId>"
    },
    "name": "activity_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
intervalsNoInclude detected intervals
activityIdYesIntervals activity ID

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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds no additional behavioral context beyond the core retrieval operation; it is not misleading but contributes little extra.

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 a single short sentence with no filler or redundant wording. It front-loads the core action and the key qualifier 'by ID' that differentiates it from list operations.

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?

For a simple fetch-by-ID tool with two well-documented parameters and annotations declaring safety and idempotence, the minimal description is sufficient. The return value is not specified but the 'get' verb in the tool name leaves little ambiguity; the description is complete enough for an agent to invoke correctly.

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%; both 'activityId' and 'intervals' are documented in the input schema. The description does not add parameter semantics beyond that, so a baseline score of 3 is appropriate.

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 uses a specific verb (Get) with a clear resource ('one Intervals activity') and retrieval method ('by ID'). This distinguishes it from siblings like activities_list, which presumably returns multiple activities.

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?

The description implies the obvious usage context: use this when you need a single activity by ID. It does not explicitly name alternatives or exclusions, but the 'one' and 'by ID' provide clear context and the get-by-ID pattern is self-explanatory among the sibling tools.

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