coros-training-mcp

Overview Schema Source Related Servers Discussions Admin

List Scheduled Workouts

list_scheduled_workouts

Retrieve scheduled workout calendar entries for a date range, returning plan-specific identifiers needed to move, remove, or replace each occurrence.

Instructions

List scheduled workout entries in a calendar-friendly format.

These are calendar occurrences, not just library workouts. Each scheduled item carries plan-specific identifiers needed for move/remove/replace flows.

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": {
      "start_day": "<start_day>",
      "end_day": "<end_day>"
    },
    "name": "list_scheduled_workouts"
  }
}

Input Schema

Name	Required	Description	Default
`end_day`	Yes	End date in YYYYMMDD format.
`start_day`	Yes	Start date in YYYYMMDD format.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 30, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations, so the description carries the burden; it implies a read operation and discloses the useful behavioral fact that each item carries plan-specific identifiers required by downstream move/remove/replace calls. It is silent on permissions/auth, result size, date-range limits, and whether empty days are included, which matters for a date-bounded listing tool.

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?

Three short sentences, front-loaded with the verb and resource, and every sentence contributes (format, disambiguation, downstream identifier note). Slightly wordier than strictly necessary but no filler.

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?

An output schema exists, so return values need not be explained, and the two required date parameters are fully documented by the schema. Gaps remain around auth requirements and how this differs from list_planned_activities, which an agent choosing among many siblings would want.

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% (both start_day/end_day documented as YYYYMMDD), so the schema already does the work and the baseline of 3 applies. The description adds no extra semantics such as inclusive/exclusive bounds or maximum range span.

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?

States a specific verb+resource ('List scheduled workout entries') and adds a distinguishing clause: these are calendar occurrences, not library workouts, which separates it from list_workouts. It does not, however, distinguish itself from the closely-named sibling list_planned_activities, leaving one ambiguity among the siblings.

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 by 'calendar-friendly format' and by the note that returned identifiers feed move/remove/replace flows, which hints at the retrieval-then-mutate pattern. But there is no explicit when-to-use / when-not-to-use statement or a named alternative (e.g., list_planned_activities vs list_workouts).

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