coros-training-mcp

Overview Schema Source Related Servers Discussions Admin

Remove Scheduled Workout

remove_scheduled_workout

Delete a planned workout from the Coros training calendar using its plan ID and entity ID to keep your schedule accurate.

Instructions

Remove a scheduled workout from the Coros training calendar.

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": {
      "plan_id": "<plan_id>",
      "id_in_plan": "<id_in_plan>"
    },
    "name": "remove_scheduled_workout"
  }
}

Input Schema

Name	Required	Description
`plan_id`	Yes	Top-level plan ID — the 'id' field returned by list_planned_activities.
`id_in_plan`	Yes	The entity's idInPlan value from list_planned_activities.
`plan_program_id`	No	The entity's planProgramId (leave empty to use id_in_plan).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 30, 2026

TDQS

B3.1/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 of behavioral disclosure. It implies a mutation with 'Remove,' but does not state whether removal is permanent, what permissions are required, or what side effects occur on the training plan.

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 front-loaded sentence with no redundant or wasted language. It is appropriately sized for a simple deletion tool.

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?

The schema is fully documented and an output schema exists, so structural information is covered. However, for a mutation tool with no annotations, the description is missing behavioral context such as permanence, authorization, and effects on the broader plan.

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 schema explains plan_id, id_in_plan, and plan_program_id in detail. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 3 applies.

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: 'Remove a scheduled workout from the Coros training calendar.' This clearly distinguishes it from scheduling or moving workouts, though it does not explicitly contrast with delete_workout or explain that it removes an occurrence from the calendar rather than deleting a workout template.

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 use this tool versus siblings such as delete_workout, replace_scheduled_workout, or move_scheduled_workout. The usage is only implied by the name and one-line purpose statement.

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