Skip to main content
Glama

delete_course

Destructive

Deletes a Garmin Connect course by ID after a preview, requiring confirmation for permanent removal.

Instructions

Delete a course from Garmin Connect.

    This cannot be undone. Call once with confirm=false (the default) to
    preview the course, then call again with confirm=true to delete it.

    Args:
        course_id: ID of the course to delete (get IDs from get_courses).
        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": {
      "course_id": "<course_id>"
    },
    "name": "delete_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the 'cannot be undone' line is reinforcement rather than new information. The genuinely additive disclosure is the dry-run/preview mode tied to confirm=false, which is not captured by any annotation and materially changes how an agent should call the tool. It stops short of describing what the preview returns or any auth requirements.

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 destructive warning, then the workflow, then structured Args — the right ordering for a dangerous operation. The confirm behavior is stated twice (in prose and in Args), a minor redundancy in an otherwise tight description.

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 2-parameter destructive tool with no output schema, the description covers the mutation's irreversibility, the two-step confirmation flow, and both parameters. Only the shape of the preview response is left unspecified, which is a small gap given no output schema exists to explain it.

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 description coverage is 0%, so the description carries the full burden, and it does document both parameters: course_id with a pointer to get_courses for valid IDs, and confirm with its default and the semantics of each value. This fully compensates for the empty schema descriptions.

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 ('Delete a course from Garmin Connect') plus the scope (a course, addressed by course_id). It is unambiguously distinct from siblings like get_courses, delete_activity, and delete_workout.

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

Usage Guidelines5/5

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

Gives an explicit two-step usage procedure: call once with confirm=false to preview, then again with confirm=true to delete. It also points to get_courses as the source of valid IDs, so the agent knows both the calling sequence and where the identifier comes from.

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