Skip to main content
Glama
Sign In
TrainingPeaks MCP

TrainingPeaks MCP

by lsantome
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tp_create_library

Create a new workout library folder to organize and categorize training sessions, making it easier to manage and retrieve workouts.

Instructions

Create a workout library folder.

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>"
    },
    "name": "tp_create_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
athleteNoTarget athlete name or ID (coach accounts only). Omit to use your own profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'Create' but does not mention side effects, permissions, idempotency, error behavior, or what happens if the library already exists. This is insufficient 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 a single, front-loaded sentence with no fluff or redundancy. It efficiently communicates the core action and resource, earning a high score for concise structure.

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

Completeness2/5

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

The description lacks essential context for a create operation without annotations or output schema. It does not explain what a library folder is, how it relates to library items, what the return value is, or any operational context. This makes it incomplete for an agent to use confidently.

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?

The schema covers the 'athlete' parameter with a description, but the 'name' parameter has no description and the tool description does not compensate. With only 50% schema coverage, the description adds no parameter-level meaning, leaving the 'name' parameter ambiguous.

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 clearly states the action ('Create') and the resource ('workout library folder'), which is distinct from siblings like tp_create_library_item. However, it does not explicitly differentiate from related tools or mention the folder concept's role, so it falls short of a perfect 5.

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 like tp_get_libraries or tp_create_library_item. There are no conditions, prerequisites, or exclusions mentioned, leaving usage implied only by the tool name.

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