Skip to main content
Glama
Sign In
TrainingPeaks MCP

TrainingPeaks MCP

by lsantome
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tp_set_workout_note

Set or update a private note on a specific TrainingPeaks workout. Clear the note by passing an empty string.

Instructions

Set or update the private workout note for a workout.

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": {
      "workout_id": "<workout_id>",
      "note": "<note>"
    },
    "name": "tp_set_workout_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesPrivate note text. Use empty string to clear.
athleteNoTarget athlete name or ID (coach accounts only). Omit to use your own profile.
workout_idYes

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 for behavioral disclosure. It only states 'Set or update' without explaining overwrite behavior, permission requirements, or failure modes. The 'private' qualifier adds some context, but not enough.

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, focused sentence with no redundant information. It is front-loaded and immediately conveys the tool's essence.

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 write tool with no output schema, the description provides a minimal but sufficient scope. However, given no annotations and a lack of behavioral details (e.g., clearing via empty string is only in the schema), the description feels incomplete for a mutation tool.

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 67%, with 'note' and 'athlete' documented in the schema. The description itself does not add parameter detail beyond the schema, but the schema already explains the note contents and the athlete context. Workout_id remains unexplained in both, but the description implies its role.

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 action ('Set or update') and the resource ('private workout note for a workout'). It distinguishes from siblings like tp_get_workout_note (read) and other note-related tools by specifying 'workout note'.

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 usage for setting/updating a workout's private note, but it does not provide explicit exclusions or alternatives. No guidance on when to use this vs. tp_update_workout or other note tools.

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