Skip to main content
Glama
Sign In
TrainingPeaks MCP

TrainingPeaks MCP

by lsantome
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tp_get_library_items

List all workout templates from a TrainingPeaks library by providing the library ID. Access template details to plan and build structured workouts.

Instructions

List templates in a workout library.

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": {
      "library_id": "<library_id>"
    },
    "name": "tp_get_library_items"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are present, so the description carries the burden. The verb 'List' implies a read-only operation, which is helpful, but there is no mention of authentication requirements, pagination, or response format. This is adequate for a simple read-only list but lacks depth.

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 concise sentence, front-loaded with the primary action. Every word earns its place, and there is no fluff.

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 tool has no output schema and a sparse description. It doesn't mention return values, ordering, filtering, or clarify the distinction between 'templates' and 'library items' from the tool name. This is incomplete for a tool with a required parameter and potential ambiguous sibling relationships.

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 description adds minimal meaning beyond the schema. It implies 'workout library' relates to library_id, but doesn't explain the athlete parameter or any constraints. With 50% schema coverage, the description should compensate but doesn't.

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 uses a specific verb ('List') and resource ('templates in a workout library'), making the primary action clear. It distinguishes from siblings like tp_get_library_item (singular) by implying plural results, but doesn't explicitly name the alternative or contrast.

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 is provided on when to use this tool versus similar siblings like tp_get_library_item or tp_get_libraries. The description only states what it does, not when it should be preferred.

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