Skip to main content
Glama

create_z2_walk_workout

Creates a steady Zone 2 walking workout with a set duration and heart-rate range, then uploads it to Garmin Connect for guided low-intensity training.

Instructions

Create a steady Z2 walking workout and upload it to Garmin Connect.

    Args:
        name: Workout name
            Max 256 characters: Garmin SILENTLY TRUNCATES longer names.
        duration_min: Main walking block duration in minutes
        hr_min: Minimum heart rate in bpm (used for description; target is Z2)
        hr_max: Maximum heart rate in bpm (used for description; target is Z2)
    

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>",
      "duration_min": "<duration_min>",
      "hr_min": "<hr_min>",
      "hr_max": "<hr_max>"
    },
    "name": "create_z2_walk_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
hr_maxYes
hr_minYes
duration_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 operation, and the description adds useful context: it uploads to Garmin Connect and warns that longer names are silently truncated. It does not cover authentication, duplicate creation, or error behavior, so it stops short of full behavioral disclosure.

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 first sentence is front-loaded and the Args block is compact and structured. The repeated note that heart-rate values are for the description and target Z2 is mildly redundant, but there is little wasted text.

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?

The tool creates and uploads an external workout, and the description covers its purpose and all parameters. With no output schema, it does not explain what the tool returns, such as a workout ID or confirmation, nor does it clarify duplicate or failure behavior.

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?

Because schema description coverage is 0%, the description must carry parameter meaning, and it documents all four parameters: name length behavior, duration units, and heart-rate units with usage for the Z2 target. It still lacks constraints such as positive durations or hr_min being below hr_max.

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 verb and resource: create a steady Z2 walking workout and upload it to Garmin Connect. The Z2 walking specialization distinguishes it from sibling workout creators such as create_walk_run_workout and 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?

The intended use is implied by the highly specific tool name and the Z2 walking scope. However, the description gives no explicit when-to-use guidance, exclusions, or comparison to sibling workout-creation tools.

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