Skip to main content
Glama
Sign In
garmin-coach-mcp

garmin-coach-mcp

by jhoy1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

schedule_workout

Schedule a saved Garmin workout onto your calendar by providing the workout ID and target date. Plan training sessions in advance to keep your fitness routine on track.

Instructions

Schedule an existing Garmin workout onto your calendar.

Args: workout_id: The workout's ID (from create_strength_workout or list_workouts). date: Target date, YYYY-MM-DD.

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

Input Schema

NameRequiredDescriptionDefault
dateYes
workout_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It states the action but does not disclose side effects, required permissions, return behavior, or failure modes. It also doesn't specify whether this modifies the calendar only or the workout itself.

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?

The description is concise, with one main sentence and a parameter list. No unnecessary words.

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 simple 2-parameter tool, the description covers the core functionality and parameters. However, it lacks information about return values, error handling, or prerequisites beyond an existing workout ID, which a fully specified tool would include.

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?

The Args section explains both parameters beyond the schema: workout_id references how to obtain it, and date specifies the exact format (YYYY-MM-DD). This compensates for the 0% schema description coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action: 'Schedule an existing Garmin workout onto your calendar.' This clearly distinguishes it from sibling tools that create, list, or delete workouts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates this tool is for existing workouts, with workout_id sourced from create_strength_workout or list_workouts, providing a direct workflow. It does not explicitly list exclusions or alternative schedule tools, but the context is clear.

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