Garmin MCP Lite

by Golden0Voyager

Overview Schema Source Related Servers Discussions Admin

Python

Local

garmin_delete_event

Delete a Garmin Connect calendar event by its event ID to remove outdated or incorrect training schedule entries.

Instructions

Delete a calendar event from Garmin Connect by its event ID.

Args: event_id: The numeric event ID (from garmin_events).

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": {
      "event_id": "<event_id>"
    },
    "name": "garmin_delete_event"
  }
}

Input Schema

Name	Required	Description	Default
`event_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.10Nov 9, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a destructive mutation. It conveys only 'delete' — nothing about whether the deletion is permanent, whether confirmation or special permissions are required, what happens on an invalid ID, or what the response contains. This is a significant gap for an irreversible operation.

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?

Two short sentences plus a compact Args block; the action and resource are front-loaded with zero filler. The Args line mostly restates the schema but is brief enough not to hurt.

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?

For a destructive single-purpose tool with no annotations, an output schema that covers return values, and an undocumented parameter, the description omits the safety and failure-mode information an agent would need before calling it. It is adequate to identify the tool but not to invoke it responsibly.

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 coverage is 0%, so the description must compensate, and it partially does by identifying the ID as numeric and pointing to garmin_events as the source. It gives no example or format detail, and 'numeric' slightly undersells the schema, which also accepts a string.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 calendar event from Garmin Connect by its event ID.' An agent can immediately tell this is the destructive counterpart to garmin_add_event/garmin_events, though the description never explicitly contrasts itself with those siblings.

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

Usage Guidelines3/5

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

The phrase '(from garmin_events)' implies the prerequisite of listing events first, which is useful usage context. However, there is no explicit when-to-use/when-not guidance, no warning about irreversibility, and no note on what to do if the ID is unknown.

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