TrainingPeaks MCP

Overview Schema Source Related Servers Discussions Admin

tp_create_equipment

Create equipment in TrainingPeaks: specify bike/shoe details like brand, model, purchase date, and starting distance. Optionally set as default or assign to an athlete (coaches).

Instructions

Add new equipment (bike or shoe).

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": {
      "name": "<name>",
      "type": "<type>"
    },
    "name": "tp_create_equipment"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`type`	Yes
`brand`	No
`model`	No
`notes`	No
`wheels`	No	Bike only
`athlete`	No	Target athlete name or ID (coach accounts only). Omit to use your own profile.
`is_default`	No
`crank_length_mm`	No	Bike only
`max_distance_km`	No
`date_of_purchase`	No	YYYY-MM-DD
`starting_distance_km`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jul 31, 2026

TDQS

B3.1/5.0

Behavior2/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 of behavioral disclosure. 'Add new equipment' implies a write operation but does not mention whether the operation is irreversible, requires specific permissions, or what the response contains. This is minimal disclosure with no extra context.

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 compact sentence with no redundancy or unnecessary words. It is front-loaded and easy to scan, though slightly too terse for the tool's complexity.

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

Completeness1/5

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

With 12 parameters, no output schema, and no annotations, the description provides almost no context. It omits key aspects like the optional athlete parameter for coach accounts, bike/shoe-specific fields, and any expected return value, making it inadequate for correct usage.

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

Parameters2/5

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

Schema description coverage is only 33%, and the description adds no parameter details beyond 'bike or shoe,' which is already captured in the type enum. It fails to compensate for the 67% of parameters (e.g., max_distance_km, starting_distance_km) that lack descriptions.

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 'Add new equipment (bike or shoe)' clearly states the action (add) and the resource (equipment), specifying the two allowed types. This distinguishes it from sibling tools like tp_get_equipment, tp_update_equipment, and tp_delete_equipment.

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?

The verb 'Add' implies this tool is for creating new equipment, but no explicit when-to-use guidance or alternative references are provided. It does not mention using tp_update_equipment for existing items, leaving usage as implied rather than explicit.

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

Deploy Server