Skip to main content
Glama

unschedule_workouts

Destructive

Remove multiple scheduled workouts from the Garmin Connect calendar in one call by passing calendar-entry IDs, leaving original workout templates intact.

Instructions

Remove multiple scheduled workouts from the Garmin Connect calendar

    Deletes multiple calendar entries in a single call. The underlying
    workout templates are left intact in your library.

    IMPORTANT: each id is a calendar-entry id (the "scheduled_workout_id"
    field from get_scheduled_workouts), not a workout id.

    Args:
        scheduled_workout_ids: List of calendar-entry ids from get_scheduled_workouts
    

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": {
      "scheduled_workout_ids": "<scheduled_workout_ids>"
    },
    "name": "unschedule_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
scheduled_workout_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds real value beyond them: the workout templates remain in the library and only calendar entries are removed. It does not address partial failure or repeat-call behavior, which matters given idempotentHint=false.

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?

The key information is front-loaded in the first two lines, and the id-provenance warning is emphasized before the Args block. The Args section largely restates the preceding warning, which is minor redundancy but costs a little tightness.

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 single-parameter destructive tool with strong annotations and no output schema, the description covers the essential decision points: what gets deleted, what is preserved, and where the ids come from. Missing only edge-case handling such as invalid or already-removed ids.

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 0%, so the description must carry the load, and it does: it identifies the list as calendar-entry ids drawn from the scheduled_workout_id field of get_scheduled_workouts and explicitly warns they are not workout ids. A concrete example of the id shape is the only thing missing.

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 ('Remove multiple scheduled workouts from the Garmin Connect calendar') and immediately adds scope ('multiple ... in a single call'), which separates it from the singular sibling and from delete_workouts by noting templates survive. An agent can pick it without opening the schema.

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 clear context: use this to delete multiple calendar entries at once, and the ids must come from get_scheduled_workouts. It does not explicitly say when to prefer the singular unschedule_workout or what to do if some ids are invalid, so it stops short of full alternative routing.

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