Skip to main content
Glama
Sign In
garmin-coach-mcp

garmin-coach-mcp

by jhoy1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_workout

Delete a saved Garmin workout using its workout ID, undoing an unwanted creation and freeing your schedule.

Instructions

Delete a saved Garmin workout (undo a created workout).

Args: workout_id: The workout's ID from list_workouts / create_strength_workout.

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_id": "<workout_id>"
    },
    "name": "delete_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
workout_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention permanence, irreversibility, or potential impact on scheduled workouts, which are critical safety traits for a deletion tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise: two sentences and a single argument definition. Every word adds value, and no filler or redundancy exists.

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 is simple with one parameter and no output schema, so the core purpose and argument source are covered. However, the lack of any destructive-effect warning (e.g., permanence, effect on schedules) leaves an important gap for a deletion action.

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?

workout_id has 0% schema description coverage, and the description compensates by explaining where to get the ID ('from list_workouts / create_strength_workout'). It does not elaborate on format beyond the schema's string type, but for a single parameter this is sufficient.

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 uses a specific verb and resource: 'Delete a saved Garmin workout', with a clarifying parenthetical 'undo a created workout'. It clearly distinguishes itself from sibling tools like create_strength_workout and list_workouts.

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?

It explains that workout_id comes from list_workouts or create_strength_workout, which instructs the agent on how to obtain the correct argument value. It does not explicitly discuss when not to use the tool or compare to alternatives, but no alternative delete tool exists among siblings.

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