Skip to main content
Glama

create_run_interval_workout

Build a repeat-based interval run workout (warmup, work reps with jog recovery, cooldown) and upload it to Garmin Connect, with optional custom heart-rate targets.

Instructions

Create a repeat-based interval run workout and upload it to Garmin Connect.

    Builds warmup -> repeats x [work interval + jog recovery] -> cooldown. Use this
    instead of create_run_workout whenever the session has more than one work
    interval (threshold reps, VO2 intervals, cruise intervals, strides).

    Work intervals target a named heart-rate zone by default, but named zones are
    usually far too wide for interval work: a threshold session at 172-180 bpm sits
    inside a Z3 that may span 158-184. Pass hr_min and hr_max together to target the
    exact bpm range, so the watch alerts as soon as the effort drifts off target.

    Recovery steps carry no target unless recovery_hr_min/max are given -- a capped
    recovery alerts constantly right after a hard rep, since heart rate lags effort.
    Recovery HR bounds require recovery_seconds > 0.

    Example -- 3 x 6 min at HR 172-180 with 3 min jogs, 12m warmup, 8m cooldown:
        repeats=3, rep_seconds=360, recovery_seconds=180,
        hr_min=172, hr_max=180, warmup_min=12, cooldown_min=8

    Args:
        name: Workout name (e.g. "Threshold 3x6min")
        repeats: Number of work intervals
        rep_seconds: Duration of each work interval in seconds
        recovery_seconds: Jog recovery between work intervals in seconds (0 to omit)
        warmup_min: Warmup duration in minutes
        cooldown_min: Cooldown duration in minutes
        hr_zone: Target zone for the work intervals (Z1-Z5, default Z4). Ignored if hr_min/hr_max are given.
        hr_min: Custom target HR range for the work intervals, minimum bpm (with hr_max)
        hr_max: Custom target HR range for the work intervals, maximum bpm (with hr_min)
        recovery_hr_min: Optional HR range for recovery jogs, minimum bpm (with recovery_hr_max)
        recovery_hr_max: Optional HR range for recovery jogs, maximum bpm (with recovery_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>",
      "repeats": "<repeats>",
      "rep_seconds": "<rep_seconds>",
      "recovery_seconds": "<recovery_seconds>",
      "warmup_min": "<warmup_min>",
      "cooldown_min": "<cooldown_min>"
    },
    "name": "create_run_interval_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
hr_maxNo
hr_minNo
hr_zoneNoZ4
repeatsYes
warmup_minYes
rep_secondsYes
cooldown_minYes
recovery_hr_maxNo
recovery_hr_minNo
recovery_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and non-idempotent writes; the description reinforces this by disclosing the external side effect of uploading to Garmin Connect. It adds real domain behavior beyond annotations: heart-rate lag making capped recovery alerts noisy, named zones being too wide for interval work, and the hr_zone-is-ignored precedence rule. It stops short of disclosing what is returned (e.g. the created workout ID) or what happens on repeated calls / failed uploads, which matters given idempotentHint=false.

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 and the sibling distinction, then behavior, then a worked example, then Args. The rationale paragraph about zone width is slightly verbose but earns its place by explaining why the hr_min/hr_max override exists. Nothing is redundant with the schema, though the prose could be tightened marginally.

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 an 11-parameter, no-output-schema, non-idempotent mutation tool, the definition covers structure, every parameter's meaning and units, inter-parameter constraints, and a fully specified example. Remaining gaps are the return value (workout ID or upload confirmation) and conflict/retry behavior for repeated creation, which no output schema exists to cover.

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 description coverage is 0%, so the description carries the full burden and does: an Args block defines all 11 parameters with units (seconds vs minutes) and defaults (hr_zone Z4). It adds dependencies the schema cannot express -- hr_min/hr_max must be passed together, recovery_hr_min/max pair together and require recovery_seconds > 0, recovery_seconds=0 omits recovery, and hr_zone is ignored when hr_min/hr_max are supplied.

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?

States a specific verb and resource ('Create a repeat-based interval run workout') plus a concrete output action ('upload it to Garmin Connect'), and describes the generated structure warmup -> repeats -> cooldown. It names the sibling it replaces (create_run_workout) and the exact condition that separates them (more than one work interval), so an agent can discriminate without opening either schema.

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

Usage Guidelines5/5

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

Explicit routing guidance: 'Use this instead of create_run_workout whenever the session has more than one work interval', backed by concrete session types (threshold reps, VO2 intervals, cruise intervals, strides). It also gives within-tool usage rules -- use hr_min/hr_max over hr_zone for exact targets, omit recovery targets by default, recovery HR requires recovery_seconds > 0.

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