Skip to main content
Glama
Sign In
Garmin MCP Server

Garmin MCP Server

by JJRPF
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

unschedule_workouts

Remove multiple scheduled workouts from your Garmin Connect calendar in a single call. Specify calendar-entry IDs to delete scheduled entries while keeping 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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are present. The description discloses the primary side effect (deletes calendar entries) and a non-side effect (templates remain), which is helpful. However, it does not mention irreversibility, permissions, or other potential side effects beyond the delete operation.

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

Conciseness5/5

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

The description is brief and well-organized, with a clear action, a side-effect clarification, and an important ID warning. Every sentence adds value and there is no redundant filler.

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?

Given the output schema exists and the sibling tools provide surrounding context, the description gives enough information to call the tool correctly. It could mention return behavior, but that is not essential because the output schema is provided.

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?

The schema only provides an array of integers with no description, but the tool description supplies critical parameter semantics: the IDs are scheduled_workout_id values from get_scheduled_workouts, not workout IDs. This is highly useful and compensates for the schema's lack of detail.

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 clearly states the verb 'Remove' and the target 'scheduled workouts' from the Garmin Connect calendar, and notes the underlying templates remain intact. It is distinct from the singular 'unschedule_workout' sibling and other workout-related tools.

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 explicitly says this is for multiple scheduled workouts in a single call and gives the crucial distinction that IDs are calendar-entry IDs, not workout IDs. It does not explicitly name the singular alternative, but the 'multiple' qualifier plus sibling names make the usage clear.

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