Skip to main content
Glama

schedule_workout

Idempotent

Schedule an existing Garmin workout from your library to a specific date on your Garmin Connect calendar, with duplicate-safe handling if it is already scheduled.

Instructions

Schedule a workout to a specific calendar date

    This adds an existing workout from your Garmin workout library
    to your Garmin Connect calendar on the specified date.

    Idempotent: if the workout is already scheduled for that date, this
    is a no-op that reports success without creating a duplicate entry.

    Args:
        workout_id: ID of the workout to schedule (get IDs from get_workouts)
        calendar_date: Date to schedule the workout in YYYY-MM-DD format
    

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>",
      "calendar_date": "<calendar_date>"
    },
    "name": "schedule_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
workout_idYes
calendar_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description goes further by explaining the idempotent behavior concretely: a repeat call is a no-op that 'reports success without creating a duplicate entry.' It also discloses that the workout must already exist in the library, which is real context not covered by annotations. It says nothing about error behavior for an invalid ID or a past date.

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?

Front-loaded with the purpose, then the mechanics, then the idempotency note, then parameter notes — a sensible order. The Args block partially restates the schema, but since schema description coverage is 0% it earns its place. Slightly verbose phrasing ('from your Garmin workout library to your Garmin Connect calendar') is the only waste.

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 mutation tool with no output schema and annotations that already cover safety and idempotency, the description supplies purpose, mechanics, idempotent return behavior, and both parameter meanings. Remaining gaps — invalid-ID errors, past-date handling, timezone — are minor.

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%, so the description must carry the load, and it does: workout_id is described as the library workout ID with a pointer to get_workouts, and calendar_date is documented as YYYY-MM-DD format. That adds the format and sourcing semantics the bare schema lacks, though it omits constraints like whether past dates or timezone considerations apply.

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 and resource ('Schedule a workout to a specific calendar date') and clarifies it moves an existing library workout onto the Garmin Connect calendar rather than creating one. Clear enough to distinguish from create_* siblings, but it never differentiates from schedule_week, schedule_workouts, or reschedule_workout by name.

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?

The Args note 'get IDs from get_workouts' gives a useful prerequisite for obtaining workout_id. However, there is no guidance on when to use this versus schedule_week (bulk), schedule_workouts, or reschedule_workout (moving an already-scheduled entry), which are the most likely confusion points.

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

Deploy Server

Other Tools