Skip to main content
Glama

delete-workout

Remove a specified workout from Garmin Connect by providing its unique workout ID.

Instructions

Delete a workout from Garmin Connect

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workoutIdYesThe workout ID to delete

Implementation Reference

  • src/tools.ts:900-911 (registration)
    Registration of the delete-workout tool with its schema (workoutId) and handler logic.
    server.tool(
      "delete-workout",
      "Delete a workout from Garmin Connect",
      {
        workoutId: z.string().describe("The workout ID to delete"),
      },
      async ({ workoutId }) => {
        const client = getClient();
        await client.delete(`workout-service/workout/${workoutId}`);
        return textResult(`Workout ${workoutId} deleted`);
      }
    );
  • Handler function that deletes a workout by ID via Garmin Connect API.
    async ({ workoutId }) => {
      const client = getClient();
      await client.delete(`workout-service/workout/${workoutId}`);
      return textResult(`Workout ${workoutId} deleted`);
    }
  • Input schema for delete-workout: requires a workoutId string.
    {
      workoutId: z.string().describe("The workout ID to delete"),
    },
  • Helper function that formats a plain text result response.
    function textResult(text: string) {
      return { content: [{ type: "text" as const, text }] };
    }
  • Helper function that returns the authenticated Garmin client, checking session exists first.
    function getClient() {
      if (!sessionExists()) {
        throw new Error(
          "No Garmin session found. The user needs to run: npx garmin-connect-mcp login"
        );
      }
      return getSharedClient();
    }
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It indicates a destructive action ('delete') but does not disclose permanence, reversibility, authorization requirements, or side effects.

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

Conciseness3/5

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

The description is a single sentence, which is concise, but it lacks important details that could be included without being verbose. It is front-loaded but overly minimal.

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

Completeness2/5

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

Given the tool's simplicity (1 param, no output schema), the description is inadequate. It fails to mention whether deletion is irreversible, any confirmation needed, or error handling, leaving the agent underinformed.

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

Parameters3/5

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

Schema description coverage is 100% for the single parameter, which already describes it as 'The workout ID to delete'. The description adds no further meaning, so baseline 3 is appropriate.

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 explicitly states the verb 'Delete' and the resource 'a workout from Garmin Connect', clearly distinguishing it from sibling tools like create-workout, get-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 Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites or conditions. It only states the action without context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/etweisberg/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server