coros-training-mcp

by dholliday3

Overview Schema Source Related Servers Discussions Admin

Python

Local

Get Workout

get_workout

Fetch a saved COROS workout program in full detail using its workout ID from list_workouts or a scheduled entry.

Instructions

Fetch one saved workout program in detail.

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

Input Schema

Name	Required	Description	Default
`workout_id`	Yes	Workout ID from list_workouts or a scheduled workout entry.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'Fetch' and 'saved' imply a safe read of an existing workout and 'in detail' indicates a fuller representation than a list, but permission requirements, error behavior, and rate limits are not addressed.

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?

One short sentence, front-loaded with the action and resource. Every word contributes and there is no filler.

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?

An output schema exists and the input schema fully documents the only parameter, so return values and parameter usage need not be repeated. The description is sufficient for a simple single-item read, though it could clarify sibling choice more explicitly.

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%, and the single workout_id parameter is already well documented as coming from list_workouts or a scheduled workout entry. The description adds no parameter detail beyond the schema, which is acceptable given full schema coverage but not value-adding.

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 states a specific verb (Fetch) and resource (one saved workout program) and clarifies verbosity with 'in detail.' It implicitly distinguishes itself from list_workouts by saying 'one,' but does not explicitly name or contrast with that sibling.

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?

Usage is implied: fetch a single saved workout after identifying it from a list or scheduled entry. The description does not explicitly state when to use this instead of list_workouts, get_workout_builder_catalog, or other workout tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.