coros-training-mcp

Overview Schema Source Related Servers Discussions Admin

List Exercises

list_exercises

List the exercise catalogue for a given sport type to resolve strength and conditioning exercises by name and ID in planned workouts.

Instructions

List the exercise catalogue for a given sport type.

Useful for resolving strength/conditioning exercises (sport_type=4) that appear in planned workouts by name and ID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_exercises"
  }
}

Input Schema

Name	Required	Description	Default
`sport_type`	No	Sport type ID. Default 4 = Strength.

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?

No annotations are provided, so the description must carry the behavioral burden. 'List' implies a read-only catalogue lookup, but pagination, result size, auth requirements, and whether the catalogue is static are all unstated. The presence of an output schema offsets some of this, keeping it at a minimum-viable level.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core purpose front-loaded and no filler. The second sentence is narrowly focused on the strength case, leaving a small gap for other sport types, but the text is efficiently sized.

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?

With one optional parameter, full schema coverage, and an output schema, the description supplies enough for correct invocation: purpose, default behavior, and the primary use case. Only catalogue freshness and result-size behavior are unaddressed, which are minor for a static-reference list 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 coverage is 100% and the single parameter already documents 'Default 4 = Strength'. The description only reinforces the sport_type=4 case in a usage context, adding marginal meaning beyond the schema, which is the baseline 3 for fully covered schemas.

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 gives a specific verb and resource ('List the exercise catalogue') plus the scoping dimension (sport type), which lets an agent tell it apart from workout-schema and catalogue siblings such as get_workout_builder_catalog. It stops short of explicitly stating how it differs from that closest sibling.

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 second sentence states a concrete use case: resolving strength/conditioning exercises (sport_type=4) that appear in planned workouts by name and ID. That is clear when-to-use guidance, but no alternative is named and there is no when-not-to-use signal.

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