Skip to main content
Glama

mywhoosh_schedule_workout

Schedules a custom cycling workout by ID on a chosen calendar date and start time in MyWhoosh.

Instructions

Put a custom workout (id from mywhoosh_list_workouts/mywhoosh_create_workout) on the MyWhoosh calendar.

date: YYYY-MM-DD, start_time: HH:MM, both local time (Europe/Berlin).

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": {
      "workout_id": "<workout_id>",
      "date": "<date>"
    },
    "name": "mywhoosh_schedule_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
start_timeNo18:00
workout_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add real context by stating that date and start_time are interpreted as local time in Europe/Berlin, which prevents a UTC mis-scheduling bug. However, it says nothing about what happens when the slot is already occupied, whether scheduling the same workout twice creates duplicates or errors, or whether a confirmation payload is returned by this mutation.

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?

Two short sentences with zero filler; the core action and its sibling pointers come first, and the format/timezone constraints follow. Every clause carries information an agent needs to construct a correct call.

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?

For a three-parameter mutation with no annotations and no output schema, the definition covers formats and timezone but omits conflict handling, duplicate-scheduling behavior, and any indication of what the call returns. These are meaningful gaps for a calendar-writing tool, though the essential call-shaping information is present.

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 description coverage is 0%, so the description must compensate, and it largely does: it gives concrete formats for date (YYYY-MM-DD) and start_time (HH:MM), states the timezone for both, and explains where workout_id comes from. Only the start_time default of 18:00 is left to the schema. This is strong compensation, short of exhaustive.

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 uses a concrete verb and resource: 'Put a custom workout ... on the MyWhoosh calendar.' It also identifies the source of the workout_id (mywhoosh_list_workouts / mywhoosh_create_workout), which helps an agent distinguish this from the creation tool. It never explicitly contrasts with mywhoosh_unschedule_workout or mywhoosh_list_scheduled_workouts, so sibling differentiation is partial rather than explicit.

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 parenthetical tells the agent to obtain the id from list_workouts or create_workout, which establishes a prerequisite. There is no explicit when-to-use or when-not-to-use guidance, and no mention of the complementary mywhoosh_unschedule_workout for reversing the action. An agent can infer the right context, but nothing is spelled out.

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