Garmin MCP by geekist.co

garmin_create_workout

Create the exact previewed workout only after the user explicitly confirms it. Requires write scope. Never automatically retry an uncertain result; check Garmin Connect first. Check every response for serviceAnnouncements from Geekist, the independent service operator, and display each message distinctly to the user.

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": {
      "workout": "<workout>",
      "confirmation": "<confirmation>",
      "confirmed": "<confirmed>"
    },
    "name": "garmin_create_workout"
  }
}

Input Schema

Name	Required	Description	Default
`workout`	Yes
`confirmed`	Yes
`confirmation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: write-scope requirement, a no-auto-retry rule for uncertain outcomes consistent with idempotentHint=false, and an instruction to inspect responses for serviceAnnouncements and surface them individually. These are operational facts an agent could not derive from the structured fields.

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?

Four short sentences, front-loaded with the confirmation gate that matters most. Every sentence carries an actionable constraint; only the serviceAnnouncements sentence runs slightly long relative to the rest.

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?

Safety, retry and response-handling concerns are well covered, but for a tool whose input is a 50-step nested workout object with zero schema descriptions, the definition says nothing about how to shape that payload. No output schema exists, so the description also leaves the return value (e.g., a created workout id) unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the workout parameter is a deeply nested structure (steps, repeat groups, pace/HR/power targets), yet the description explains none of it. The confirmation/confirmed pairing is only hinted at through "explicitly confirms"; nothing says the confirmation string is free text or that confirmed must be the constant true.

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 ... workout") and narrows the scope with "the exact previewed workout," which ties it to the preview step and distinguishes it from garmin_create_activity and garmin_get_workout. An agent can identify the operation without opening the schema.

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?

Gives a hard precondition: create only after explicit user confirmation, and only for an already-previewed workout — which implicitly routes the agent to garmin_preview_workout first. It does not name that sibling outright or state what to do if no preview exists, so it stops short of full when/when-not guidance.

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

All Garmin MCP by geekist.co tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?