Skip to main content
Glama
tildecomunicacion

TrainingPeaks MCP Server

tp_create_workout

Plan and save a TrainingPeaks workout with required date, sport, and title. Optionally include duration, distance, TSS, description, or interval structure.

Instructions

Create a planned TrainingPeaks workout on a specific date (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS) with optional planned duration, distance, TSS, and description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_strYesWorkout planned date (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS for planned start time)
sportYesSport type
titleYesWorkout title
duration_minutesNoOptional planned duration in minutes
distance_kmNoOptional planned distance in kilometers
tss_plannedNoOptional planned Training Stress Score (TSS)
descriptionNoOptional planned workout description
structureNoOptional interval structure as a JSON object. Structure format: {'primaryIntensityMetric': 'percentOfThresholdPace'|'percentOfFtp', 'steps': [{'name': 'Warm Up', 'duration_seconds': 600, 'intensity_min': 50, 'intensity_max': 60, 'intensityClass': 'warmUp'}, {'type': 'repetition', 'reps': 4, 'steps': [{'name': 'Active Block', 'duration_seconds': 300, 'intensity_min': 88, 'intensity_max': 93, 'intensityClass': 'active'}, {'name': 'Recovery', 'duration_seconds': 120, 'intensity_min': 50, 'intensity_max': 60, 'intensityClass': 'rest'}]}]}. For Run (running) workouts, default is 'percentOfThresholdPace' (Pace). For Bike/MtnBike (cycling) workouts, default is 'percentOfFtp' (Power/Watts).
Behavior2/5

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

With no annotations, the description carries the full burden. It only states creation but does not disclose potential side effects (e.g., overwriting existing workouts), error conditions, or required permissions. This is insufficient for a creation tool.

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 description is a single sentence that front-loads the main action. It is efficient but could be shortened slightly by moving date format details to the parameter description.

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?

Given 8 parameters and no output schema or annotations, the description covers the main action and optional fields but lacks information about expected return values, error handling, or authentication requirements. Adequate but not comprehensive.

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 coverage is 100%, so the description adds value mainly for the structure parameter (detailed example and defaults) and date format specification. Other parameters are well-covered by schema, so baseline 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?

The description clearly states the verb 'Create' and resource 'planned TrainingPeaks workout' with specific optional fields. It is distinct from sibling tools (e.g., tp_delete_workout, tp_get_workouts) as the only creation tool.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., tp_get_workouts for reading). It does not state any prerequisites or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tildecomunicacion/trainingpeaks_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server