Skip to main content
Glama

create_run_workout

Create and upload a continuous run workout to Garmin Connect with warmup and cooldown walks, targeting a named heart-rate zone or a custom bpm range for accurate in-range guidance.

Instructions

Create a continuous run workout and upload it to Garmin Connect.

    Builds a single uninterrupted run interval with warmup and cooldown walks.

    Targets a named Garmin heart-rate zone by default. Named zones (Z1-Z5)
    don't line up with every real training target -- e.g. a 136-148 bpm
    Zone 2 goal straddles Garmin's Z2 (118-137) and Z3 (138-157). Pass
    hr_min and hr_max together to target that exact bpm range instead;
    the watch will then show "in range" only for the range you actually
    want, not a whole zone that over- or under-shoots it.

    Args:
        name: Workout name (e.g. "Step 8 - 30min continuous")
            Max 256 characters: Garmin SILENTLY TRUNCATES longer names.
        run_seconds: Duration of the run in seconds
        warmup_min: Warmup walk duration in minutes
        cooldown_min: Cooldown walk duration in minutes
        hr_zone: Target heart-rate zone (Z1-Z5, default Z3). Ignored if hr_min/hr_max are given.
        hr_min: Optional custom target heart rate range, minimum bpm (must be given with hr_max)
        hr_max: Optional custom target heart rate range, maximum bpm (must be given with hr_min)
    

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": {
      "name": "<name>",
      "run_seconds": "<run_seconds>",
      "warmup_min": "<warmup_min>",
      "cooldown_min": "<cooldown_min>"
    },
    "name": "create_run_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
hr_maxNo
hr_minNo
hr_zoneNoZ3
warmup_minYes
run_secondsYes
cooldown_minYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, open-world, non-idempotent write; the description adds meaningful extras beyond them: it uploads to Garmin Connect, names are SILENTLY TRUNCATED past 256 characters, and hr_zone is ignored when hr_min/hr_max are supplied. It doesn't say what comes back after upload (workout ID, success confirmation) or whether repeated calls create duplicates.

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, followed by behavior and zone-selection rationale, then a well-formatted Args block. The zone-vs-bpm paragraph is longer than strictly necessary but its concrete example earns most of its space.

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?

Annotations cover the safety profile and there is no output schema, so the description's burden is behavioral and parametric — both are largely met. The remaining gap is the post-upload result (what the tool returns, whether the remote workout is addressable afterwards), which an agent would want for follow-up calls like schedule_workout.

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

Parameters5/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 all parameter meaning and it does: every one of the 7 params is defined with units (seconds vs minutes), the Z1-Z5 domain, the default Z3, the 256-character name limit, and the mutual-dependency rule that hr_min and hr_max must be given together and override hr_zone.

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?

Opens with a specific verb+resource: 'Create a continuous run workout and upload it to Garmin Connect', then clarifies the structure ('a single uninterrupted run interval with warmup and cooldown walks'). This implicitly separates it from interval-style siblings (create_run_interval_workout, create_walk_run_workout) without naming them, so an agent gets the gist but no explicit disambiguation.

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?

Strong guidance on which heart-rate targeting mode to choose: named zones by default, or hr_min/hr_max together when a real target straddles Garmin's zone boundaries, with the concrete 136-148 vs Z2/Z3 example. It gives no guidance, however, on when to pick this tool over the sibling workout-creation tools (interval, walk-run, Z2 walk).

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