coros-training-mcp

Overview Schema Source Related Servers Discussions Admin

Create Strength Workout

create_strength_workout

Create a structured strength workout program in COROS by specifying exercises, sets, and rest intervals to build consistent training plans.

Instructions

Create a new structured strength workout program.

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": {
      "name": "<name>",
      "exercises": "<exercises>"
    },
    "name": "create_strength_workout"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Workout name.
`sets`	No	Number of circuit repetitions (default 1).
`exercises`	Yes	- origin_id (str): exercise catalogue ID from list_exercises - name (str): T-code name (e.g. "T1061") - overview (str): sid_ key (e.g. "sid_strength_squats") - target_type (int): 2=time in seconds, 3=reps - target_value (int): number of seconds or reps - rest_seconds (int): rest after this exercise (default 60)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 30, 2026

TDQS

C2.9/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 behavioral burden, and it says nothing beyond 'create'. It does not disclose validation rules, whether duplicate names are rejected, permission/auth requirements, or whether partial exercise data is tolerated — meaningful gaps for a write operation.

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?

A single front-loaded sentence with no filler, so there is nothing to trim. Its brevity is efficient rather than padded.

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?

For a mutation tool with no annotations in a dense family of workout CRUD tools, the description should at least point to the schema/catalog sources needed to build the exercises array. Output schema existence excuses explaining return values, but the call prerequisites are left unaddressed.

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 100%, and the nested exercise fields, target_type semantics, and defaults are all documented in the schema, so the description adds nothing further. Baseline 3 applies since the schema does the heavy lifting; note the description also omits the fact that 'sets' means circuit repetitions.

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 and resource ('Create a new structured strength workout program'), which distinguishes it from create_run_workout and create_bike_workout by modality. It stops short of noting how it relates to the generic create_workout sibling.

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?

There is no guidance on when to pick this over create_workout, nor any mention of the apparent prerequisites in the sibling set (get_strength_workout_schema or list_exercises for origin_id). The agent must infer all of this from tool names alone.

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