Skip to main content
Glama
Sign In
TrainingPeaks MCP

TrainingPeaks MCP

by lsantome
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tp_pair_workout

Match a completed workout to its planned counterpart, merging actual data into the planned session for unified tracking.

Instructions

Pair a completed workout with a planned workout. Attaches the completed data to the planned workout, merging them into one.

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": {
      "completed_workout_id": "<completed_workout_id>",
      "planned_workout_id": "<planned_workout_id>"
    },
    "name": "tp_pair_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
athleteNoTarget athlete name or ID (coach accounts only). Omit to use your own profile.
planned_workout_idYesThe ID of the planned workout to pair with.
completed_workout_idYesThe ID of the completed (actual) workout.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/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. It indicates the operation merges completed data into the planned workout, implying a mutation, but does not state whether the operation is reversible, requires special permissions, or what happens to the completed workout record. This is a significant gap for a mutation tool.

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 two short sentences with no unnecessary words or repetition. It is front-loaded and to the point.

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?

For a simple pairing operation with two required IDs, the description conveys the core purpose. However, it lacks details about side effects, reversibility, and return format, and with no output schema or annotations, the agent may not know what to expect after invocation. It is minimally complete 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 description coverage is 100% for all three parameters, so the schema already explains the parameters thoroughly. The description adds no per-parameter detail beyond the overall purpose, which is acceptable given the high schema coverage.

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 tool's function: pairing a completed workout with a planned workout and attaching the completed data. It uses a specific verb and resource, and the phrase 'merging them into one' distinguishes it from related tools like tp_unpair_workout.

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 description implies the use case (when you have a completed and planned workout to link) but provides no explicit guidance on when to use this tool vs. alternatives or any prerequisites. Sibling tools like tp_unpair_workout exist, but no comparative direction is given.

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