Skip to main content
Glama

delete_workout

DestructiveIdempotent

Permanently delete a workout template. This cannot be undone. Deleting a workout also removes it from any schedules and from the user's Garmin device. App default workouts cannot be deleted.

Args: workout_id: The workout's id, as a tool result lists it. Never show it to the user. workout_name: The workout's name, as that result lists it. A name that does not match the id is refused and nothing is deleted.

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

Input Schema

NameRequiredDescriptionDefault
workout_idYesThe workout's workout_id, as a tool result lists it
workout_nameYesThe workout's current name, as its tool result lists it. Checked against workout_id; a mismatch is refused.

Output Schema

NameRequiredDescriptionDefault
workout_idYes
folder_nameNo
workout_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / folder_name
      Removed value: -{
      -  "description": "Folder that holds the workout, to disambiguate duplicate names. Use \"My Workouts\" for a workout not in any folder.",
      -  "type": "string"
      -}
    • addedInput schema / properties / workout_id
      Added value: +{
      +  "description": "The workout's workout_id, as a tool result lists it",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / workout_name / description
      Previous value: -"The exact name of the workout template to delete"New value: +"The workout's current name, as its tool result lists it. Checked against workout_id; a mismatch is refused."
    • addedInput schema / properties / workout_name / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
      -  "workout_name"
      -]New value: +[
      +  "workout_id",
      +  "workout_name"
      +]
    • addedOutput schema / properties / workout_id
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "workout_name"
      -]New value: +[
      +  "workout_id",
      +  "workout_name"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real behavioral payload beyond them: the deletion propagates to schedules and the user's Garmin device, is irreversible, and is blocked for app defaults. Those side effects are not derivable from the annotation flags.

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-loads the irreversible nature and side effects before the parameter details, which is the right ordering for a destructive tool. The Args block partly restates the schema's own descriptions (e.g., 'as a tool result lists it'), which is mildly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the three things an agent needs before an irreversible call: what gets destroyed, what else is affected, and what input is rejected. An output schema exists, so return values need not be explained, leaving no material gap.

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 100%, so the baseline is 3; the description nevertheless adds meaning, notably the display constraint 'Never show it to the user' for workout_id and framing workout_name as a confirmation guard checked against the id. The mismatch-refusal behavior is already in the schema, so the gain over structured data is modest rather than large.

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 ('Permanently delete a workout template') and immediately qualifies the scope with 'This cannot be undone', which separates it cleanly from update_workout and unschedule_workout. An agent can identify the operation without consulting the sibling list.

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 clear when-not condition: 'App default workouts cannot be deleted', which prevents a known class of failed calls. It does not explicitly route to an alternative (e.g., unschedule_workout for removing from a schedule only), so it stops short of full when/when-not/alternatives guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources