Skip to main content
Glama

mywhoosh_list_scheduled_workouts

List MyWhoosh calendar entries between two inclusive local-time dates to review scheduled cycling workouts. Pass start and end dates as YYYY-MM-DD.

Instructions

List MyWhoosh calendar entries between two dates (YYYY-MM-DD, inclusive, local time).

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_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "mywhoosh_list_scheduled_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does deliver real behavioral detail: the date format is YYYY-MM-DD, the boundaries are inclusive, and interpretation is in local time. It does not state the ordering of results, pagination or result limits, or what happens when a range contains no entries, which are material gaps for an unannotated list tool.

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?

A single sentence with the action and scope front-loaded and the format/boundary qualifiers in parentheses where they belong. Nothing is redundant or padded.

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

Completeness4/5

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

For a two-parameter read tool with no output schema and no annotations, the description covers the essentials needed to call it correctly. It falls short only on result-set behavior (ordering, limits, empty results) and on making the split from mywhoosh_list_workouts unambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the properties only carry titles like "Start Date" and "End Date" — so the description must compensate, and it does by fixing the exact string format (YYYY-MM-DD, inclusive, local time). The only thing it leaves unstated is what happens on a malformed date or if start_date is after end_date.

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 pairs the specific verb "List" with the specific resource "MyWhoosh calendar entries" and adds a date-range scope, so the agent knows exactly what is returned. It is not explicitly contrasted with the sibling mywhoosh_list_workouts (the workout library), so the differentiation is left to inference from the word "calendar".

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 rather than stated: the phrase "calendar entries" suggests this is the scheduled-workout view rather than the workout library, and the required date range signals it is meant for bounded queries. There is no explicit when-to-use / when-not-to-use guidance and no named alternative such as mywhoosh_list_workouts or mywhoosh_schedule_workout.

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