Skip to main content
Glama

create_walk_run_workout

Build and upload a walk/run interval workout to Garmin Connect from run, walk, repeat, warmup, cooldown, and heart-rate zone inputs, returning the new workout ID.

Instructions

Create a walk/run interval workout and upload it to Garmin Connect.

    Builds the internal Garmin JSON automatically and returns the new workout ID.

    Args:
        name: Workout name (e.g. "W3 Mié 2:2")
            Max 256 characters: Garmin SILENTLY TRUNCATES longer names.
        run_seconds: Duration of each run interval in seconds
        walk_seconds: Duration of each walk/recovery interval in seconds
        repeats: Number of run/walk repetitions
        warmup_min: Warmup duration in minutes
        cooldown_min: Cooldown duration in minutes
        hr_zone: Target heart-rate zone (Z1-Z5, default Z3)
    

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>",
      "walk_seconds": "<walk_seconds>",
      "repeats": "<repeats>",
      "warmup_min": "<warmup_min>",
      "cooldown_min": "<cooldown_min>"
    },
    "name": "create_walk_run_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
hr_zoneNoZ3
repeatsYes
warmup_minYes
run_secondsYes
cooldown_minYes
walk_secondsYes

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 readOnly=false, openWorld=true, and idempotent=false, so the bar is lower. The description still adds real value beyond them: it says the Garmin JSON is built automatically, that the new workout ID is returned, and warns that Garmin silently truncates names over 256 characters. It does not cover authentication or failure behavior for the upload.

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 two-sentence summary is front-loaded with the action and the external effect, followed by a well-organized Args block. Every line carries parameter detail, though the docstring formatting is slightly verbose for the amount of content.

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 seven-parameter mutation tool with no output schema, the description covers the input semantics, the return value (workout ID), and the key gotcha (silent name truncation). It omits what happens on upload failure or whether the workout is auto-scheduled, which are minor gaps given the annotations already flag the write and non-idempotent nature.

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 so for all seven parameters, giving units (seconds for intervals, minutes for warmup/cooldown), the repetition count, the Z1-Z5 range and Z3 default for hr_zone, and an example name format plus the truncation limit. This adds substantial meaning the schema does not provide.

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 names a specific verb and resource ('Create a walk/run interval workout') and states the external effect ('upload it to Garmin Connect'), which lets an agent distinguish it from a plain run workout. It stops short of explicitly differentiating from close siblings such as create_z2_walk_workout or create_run_interval_workout.

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 interval-workout framing, but there is no explicit when-to-use or when-not-to-use guidance, and no mention of which sibling to choose for a steady-run or Z2 walk session. The agent must infer the selection criteria from the name and description alone.

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