Skip to main content
Glama
cygnusb

coros-mcp

by cygnusb
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

save_workout_template

Save a reusable cycling, running, or interval workout to your Coros library as a template, ready to sync to your watch for guided execution.

Instructions

Save a REUSABLE cycling/intervals/running workout TEMPLATE to the Coros library.

⚠️ This persists to the library indefinitely. Use ONLY when the user explicitly asks to "save as a template", "create a workout in my library", "add to my workout list", or otherwise indicates they want a reusable template.

For a ONE-OFF workout for a specific date — the common case — use schedule_workout instead. That tool builds the workout inline and leaves no library residue.

If the user's intent is unclear, ASK THEM: "Do you want this saved as a reusable template in your library, or just scheduled as a one-off for [date]?" Don't guess.

The saved template appears in the Coros app under Workouts and can be synced to the watch for guided execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesWorkout name (e.g. "Z2 Erholung 60min").
stepsYesList of workout steps. Each step is either a plain step or a repeat group. Plain step: - name (str): step label, e.g. "10:00 Warm-up" - duration_minutes (float): step duration in minutes - intensity_low (int): lower intensity target (watts, BPM, etc. depending on intensity_type) - intensity_high (int): upper intensity target (0 = open-ended) Note: power_low_w / power_high_w are accepted as legacy aliases for intensity_low / intensity_high. Repeat group (for intervals): - repeat (int): number of repetitions - steps (list[dict]): sub-steps (same format as plain steps) Example: [
sport_typeNoSport type ID, in the ACTIVITY namespace (the same IDs list_activities returns). Default 2 = Indoor Cycling (indoor trainer). - Cycling: 2 = Indoor Cycling (indoor trainer), 200 = Road Bike (outdoor), 201 = Indoor Cycling (alt) - Running: 100 = Running, 102 = Trail Running, 103 = Track Running Running IDs are mapped internally to the workout-API wire ID (sportType=1) and given the metadata block COROS requires for runs. Do NOT pass 1 directly — it's the internal wire ID and is rejected.
intensity_typeNoIntensity type ID. Defaults per sport when omitted: runs → 2 (HR), cycling → 6 (power in watts). Other IntensityType values: 1=weight, 2=HR, 3=pace, 4=speed, 5=none, 6=power, 7=cadence

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

The description warns that the action persists to the library indefinitely, adding clarity beyond the readOnlyHint=false annotation. It also explains the template appears in the Coros app and can be synced, providing behavioral context not captured in annotations.

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?

Though slightly long, every section earns its place: purpose, warning, alternative, ambiguity handling, and outcome. It is well-structured with bold warnings and a clear quoted question, making it scannable and effective without redundancy.

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

Completeness5/5

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

Given the tool's complexity and ambiguity (template vs one-off), the description covers use cases, persistence, sibling distinction, and parameter mapping completely. Output schema exists, so return value explanation isn't needed. It handles unclear intent proactively.

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%, so the baseline is 3. The description doesn't add additional param-level meaning beyond what the schema already provides (e.g., sport_type mapping, intensity_type defaults, step format). No extra semantic help is needed.

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 saves a REUSABLE workout template to the Coros library, using specific verbs and resource. It also contrasts with schedule_workout for one-off workouts, distinguishing it from a key sibling.

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

Usage Guidelines5/5

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

Explicitly states when to use (user asks to save as template, create in library, etc.) and when not to (one-off workouts → use schedule_workout). Also instructs to ask the user if intent is unclear, providing a direct quoting example.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cygnusb/coros-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server