Skip to main content
Glama
Sign In
TrainingPeaks MCP

TrainingPeaks MCP

by lsantome
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tp_get_workouts

List workouts within a date range, filtering by all, planned, or completed. Specify an athlete for coach accounts to retrieve their training schedule.

Instructions

List workouts in date range. Query only days needed. Max 90 days.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "tp_get_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter: all, planned, or completedall
athleteNoTarget athlete name or ID (coach accounts only). Omit to use your own profile.
end_dateYesYYYY-MM-DD
start_dateYesYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It adds the key constraint of a 90-day maximum and encourages minimal date ranges, but it does not mention what happens when the range exceeds the limit, pagination, or ordering. More detail could be added for full transparency.

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?

Three short sentences deliver the purpose and key usage constraint without any waste. The description is front-loaded and every statement earns its place.

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

Completeness4/5

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

For a list tool with a fully documented schema, the description is adequate: it specifies the date-range scope and the 90-day limit. It does not describe return format, but the meaning of 'list workouts' is clear, and the schema covers parameter specifics. Slightly more detail on error handling or response structure could push it to 5.

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 baseline is 3. The description aligns with the start_date and end_date parameters by mentioning date range, and 'Query only days needed' reinforces their intended use, but it does not add significant new meaning beyond the schema's own parameter 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 clearly states the tool lists workouts within a date range, which is a specific verb+resource+scope. It distinguishes itself from sibling tools like tp_get_workout (single workout) and other workout analytics tools by focusing on listing within a range.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance on when to use the tool: list workouts in a date range, and explicitly advises to query only needed days and warns about the 90-day limit. It does not name alternatives but the context is sufficient.

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