Skip to main content
Glama

create_strength_workout

Create reps-based strength workouts with exercise sets and rest structure, then upload them to Garmin Connect for use on your device.

Instructions

Create a strength workout and upload it to Garmin Connect.

    Each exercise becomes a reps-based step; when sets > 1 the exercise is
    emitted as a repeat group of that many iterations (work + rest per set),
    so Garmin shows the real set count. The name is kept in the step
    description; it is also sent as exerciseName, which Garmin only retains when
    it matches one of its own exercise keys (e.g. "FARMERS_CARRY").

    Args:
        name: Workout name
            Max 256 characters: Garmin SILENTLY TRUNCATES longer names.
        exercises: List of dicts with keys: name, sets, reps, rest_seconds and an
            optional category. Category is omitted from the payload when not
            given; Garmin accepts that. When given it must be one of Garmin's
            exercise categories (e.g. SQUAT, DEADLIFT, PUSH_UP, CARRY, SLED) —
            anything else, including "UNASSIGNED" and "OTHER", is rejected with
            400 Invalid category. Full list:
            https://connect.garmin.com/web-data/exercises/Exercises.json
    

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>",
      "exercises": "<exercises>"
    },
    "name": "create_strength_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
exercisesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Substantially exceeds the annotations, which only declare a non-read-only, non-idempotent, open-world write. It discloses the repeat-group emission model for sets>1, that names are silently truncated past 256 characters, that exerciseName is only retained for matching Garmin keys, and that invalid categories return a 400. What it omits is the return value after upload and whether duplicate uploads 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 action in the first line, then details layered by importance: emission behavior, naming behavior, then per-argument notes. Slightly long with the raw documentation URL, but no sentence is filler, and each caveat (truncation, 400 error) prevents a real failure.

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 two-parameter write tool with no output schema, the mechanics, limits, and failure modes are well covered. The notable gap is what the call returns (workout ID, URL, confirmation) so an agent cannot chain into schedule_workout or push_workout_to_device without guessing.

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?

Schema coverage is 0% and the exercises array is an untyped object with additionalProperties, so the schema provides essentially nothing. The description fully compensates by enumerating every exercise key (name, sets, reps, rest_seconds, optional category), the category constraint and its validation failure mode, and the 256-character name limit.

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?

Opens with a specific verb and resource ("Create a strength workout") plus the destination system (Garmin Connect), which distinguishes it at a glance from the run/walk workout creators in the sibling set. The follow-up sentences on how exercises map to steps reinforce that this tool is the strength-specific one.

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 only implied by the resource type: an agent can infer it should call this for strength workouts and the siblings for run workouts, but the description never states when to use it, when not to, or names any alternative tool. No prerequisites or ordering guidance (e.g., whether to schedule or push afterward) are given.

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