Skip to main content
Glama

delete_workout

Destructive

Permanently removes a workout from your Garmin Connect library. Preview it first with confirm=false, then delete with confirm=true. Get workout IDs from get_workouts.

Instructions

Delete a workout from Garmin Connect

    Permanently removes a workout from your Garmin Connect workout library.
    This cannot be undone. Call once with confirm=false (the default) to
    preview the workout, then call again with confirm=true to delete it.

    Args:
        workout_id: ID of the workout to delete (get IDs from get_workouts)
        confirm: Must be true to actually delete. Default false returns a preview.
    

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
confirmNo
workout_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds substantive behavior: the deletion is permanent, cannot be undone, and the default call is a non-destructive preview rather than an actual delete. What the preview returns and any permission requirements are not described, keeping it short of a 5.

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?

Content is front-loaded with the action and the irreversibility warning before the mechanics, and every sentence carries weight. The Args block partially restates what the schema already shows (types, default), which is slightly redundant but still adds semantics.

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 destructive tool with no output schema, the definition covers purpose, danger, and the confirm protocol. The only real gap is what the preview or successful deletion returns, which an agent might want before calling.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden, and it does: workout_id is identified as the target ID sourced from get_workouts, and confirm is explained as the gate that must be true to delete with false yielding a preview. Both parameters gain meaning that the bare schema does not provide.

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 opening line names a specific verb and resource ('Delete a workout from Garmin Connect') and the second sentence narrows scope to the workout library while stating permanence. This clearly separates it from read-oriented siblings like get_workouts and get_workout_by_id.

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 prescribes an explicit two-step workflow (preview with confirm=false, then confirm=true) and points to get_workouts for obtaining IDs, which is real when-and-how guidance. It does not address the bulk sibling delete_workouts or say when to prefer one over the other.

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