Skip to main content
Glama

Garmin Connect (treinos)

by io.github.mcp-dir

garmin_submit_workout

Create a new structured workout on Garmin Connect. Body must match Garmin API (workoutName, sportType, workoutSegments with ExecutableStepDTO / RepeatGroupDTO). You may omit displayOrder/displayable everywhere and the endCondition on RepeatGroupDTO — the server normalizes them automatically (see workout.description). Multi-sport: sportTypeKey multi_sport (typically sportTypeId 5) with one segment per discipline. Returns workout_id and raw_data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNo
workoutYes

TDQS

A4.3/5.0
Behavior4/5

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

Discloses server normalization of omitted fields and automatic handling of certain properties, adding value beyond annotations.

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?

Concise (3 sentences) and front-loaded, though could be more structured with bullets. Still efficient.

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?

Adequately covers complex nesting and multi-sport scenarios. Notes return value despite no output schema.

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?

Despite 0% schema description coverage, the description explains the 'workout' parameter structure in detail, including DTO names and multi-sport specifics.

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 clearly states the action ('Create a new structured workout') and the resource ('on Garmin Connect').

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

Usage Guidelines4/5

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

Provides detailed guidance on body structure, omittable fields, and multi-sport handling. Implicitly distinguishes from create/edit/delete siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Garmin Connect (treinos) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose. The Garmin-specific tools each handle a unique operation on workouts or accounts, and the platform tools (authenticate, connect, marketplace, etc.) are separate and easily distinguishable.

Naming Consistency2/5

The naming is inconsistent: Garmin tools use a consistent 'garmin_verb_noun' pattern, but the platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) lack any prefix or pattern, creating a mismatch.

Tool Count4/5

With 16 tools, the count is slightly above the typical sweet spot but still justified. The domain of workout management requires several operations, and the platform utilities are essential for the server's operation within the MCP ecosystem.

Completeness4/5

The Garmin workout tools cover the full lifecycle: create, retrieve, update, delete, plus scheduling. Listing accounts and the platform utilities round out the surface. Minor gaps (e.g., no tool to fetch activities) are acceptable given the server's focus on 'treinos' (workouts).

Resources