coros-training-mcp

Overview Schema Source Related Servers Discussions Admin

List Planned Activities

list_planned_activities

Retrieve scheduled activities from the Coros training calendar for a specified date range using start and end dates in YYYYMMDD format.

Instructions

List planned (scheduled) activities 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": {
      "start_day": "<start_day>",
      "end_day": "<end_day>"
    },
    "name": "list_planned_activities"
  }
}

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

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 full disclosure burden, yet it says nothing about authentication requirements, result limits/pagination, date-range constraints, or what happens with an empty calendar. It does implicitly convey a read-only listing operation and identifies the data source (Coros training calendar), which is the only real behavioral signal.

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 or repetition. Slightly redundant in saying both 'planned' and '(scheduled)', but efficiently structured.

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 needn't be explained, and the parameters are fully documented. What is missing is the disambiguation from the near-identical sibling list_scheduled_workouts, which is the main question an agent has when choosing this 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 description coverage is 100% with both required date parameters documented as YYYYMMDD strings, so the baseline is 3. The description adds no semantics beyond the schema — nothing about inclusive/exclusive bounds, maximum range, or timezone.

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 ('List') and a clearly bounded resource ('planned/scheduled activities from the Coros training calendar'), and the parenthetical clarifies the planned-vs-completed distinction relative to list_activities. However, it does not differentiate itself from the close sibling list_scheduled_workouts, so an agent cannot route between the two from the text alone.

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 explicit statement of when to use this tool versus list_activities, list_scheduled_workouts, or schedule_workout, and no exclusions or prerequisites. Usage can only be inferred from the name.

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