Skip to main content
Glama

get_scheduled_workouts

Read-only

Retrieve scheduled Garmin Connect workouts between two dates, including scheduled dates and completion status, to review your training calendar.

Instructions

Get scheduled workouts between two dates with curated summary list

    Returns workouts that have been scheduled on the Garmin Connect calendar,
    including their scheduled dates and completion status.

    Args:
        start_date: Start date in YYYY-MM-DD format
        end_date: End date 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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_scheduled_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine value by stating the return contents ('scheduled dates and completion status') and the 'curated summary list' form, but says nothing about result volume, ordering, or empty-range behavior.

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?

The tool's function is stated up front, followed by return-content detail and a compact Args block. There is mild redundancy between the opening line and the 'Returns workouts that have been scheduled...' sentence, but nothing is padding.

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-only listing tool with no output schema, the definition covers purpose, the date format requirement, and what comes back (dates plus completion status). Missing pagination or ordering notes are minor at this complexity.

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%—the schema only carries titles like 'Start Date'—so the description must compensate, and it does by specifying the required YYYY-MM-DD format for both parameters along with the start/end semantics. It stops short of clarifying inclusive/exclusive boundaries or timezone handling.

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 specific verb and resource ('Get scheduled workouts between two dates') and scopes it to workouts 'scheduled on the Garmin Connect calendar,' which separates it from plain workout-listing siblings like get_workouts or get_training_plan_workouts. It does not explicitly name an alternative, so it falls short of a 5.

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 the 'scheduled on the Garmin Connect calendar' framing and the required date range, but there is no explicit statement of when to prefer this over get_workouts, get_training_plan_workouts, or get_garmin_coach_workouts. The agent must infer the distinction from the wording.

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