Skip to main content
Glama
Sign In
intervals.mcp

intervals.mcp

by ryansheppard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_athlete

Retrieve athlete profile data with sport-specific zones and performance thresholds to analyze training metrics and personalize workout plans.

Instructions

Get athlete profile including sport zones and thresholds.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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. It partially discloses what data is returned ('sport zones and thresholds'), but lacks information on caching behavior, authentication requirements, rate limits, or error conditions. It implies a read-only operation through the verb 'Get'.

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, efficient sentence of seven words. It is front-loaded with the action verb and contains no redundant or wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without an output schema, the description partially compensates by mentioning specific return content ('sport zones and thresholds'), but lacks details on response structure, data types, or complete field enumeration. Given the tool's simplicity (no inputs) and lack of annotations, this is minimally adequate but has clear gaps.

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?

The input schema contains zero parameters. According to the scoring rules, zero parameters warrant a baseline score of 4, as there are no parameter semantics to clarify beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description provides a specific verb ('Get'), resource ('athlete profile'), and scope ('including sport zones and thresholds'). It implicitly distinguishes from siblings (get_activities, get_fitness, etc.) by focusing on static profile data rather than time-series or activity data, though it doesn't explicitly differentiate from them.

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

Usage Guidelines2/5

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

No guidance provided on when to use this tool versus alternatives like get_fitness (which may overlap with 'thresholds') or get_wellness. No prerequisites or exclusion criteria are mentioned.

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