Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_gear

Destructive

Deletes a Garmin Connect gear item and its activity history. This action is irreversible; confirm with the user before calling.

Instructions

Deletes a piece of gear and its activity history. IRREVERSIBLE. DELETE /gear-service/gear/v2/{gearUUID}, resolves null on success (204). The UUID must be HYPHENATED: getGear returns them WITHOUT hyphens and that form 404s, so this method re-inserts them for you when handed the bare 32-char form; only hand-rolled URLs hit the 404. IRREVERSIBLE: confirm with the user before calling.

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": {
      "gearUUID": "<gearUUID>"
    },
    "name": "delete_gear"
  }
}

Input Schema

NameRequiredDescriptionDefault
gearUUIDYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this destructive, but the description adds real behavioral context beyond them: the DELETE route, the 204/null-on-success return, and the non-obvious side effect that gear activity history is destroyed along with the record. The hyphenation quirk and its 404 consequence are pure added value.

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?

Purpose is front-loaded and the UUID caveat is well placed, but 'IRREVERSIBLE' is asserted twice and the endpoint/route detail is arguably internal trivia for an agent-facing description. Minor redundancy rather than bloat.

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

Completeness5/5

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

No output schema exists, and the description supplies the success semantics (204/null), the destructive side effects, and the confirmation requirement. Nothing an agent needs in order to call this safely is missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries full burden for the sole parameter — and it does: it explains that the UUID must be hyphenated, that `getGear` returns the unhyphenated 32-char form, and that this method re-inserts hyphens so the caller need not. That is meaningfully more than the bare `{"gearUUID": string}` schema.

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 ('Deletes') and resource ('a piece of gear'), and crucially scopes the blast radius by noting it also removes the gear's activity history. This distinguishes it from sibling `remove_gear_from_activity`, which detaches but does not destroy the gear record.

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 preconditions: confirm with the user before calling, and the exact UUID form to supply. It never explicitly routes the agent away from alternatives such as `remove_gear_from_activity` or `delete_activity`, so the when-not guidance is implied rather than stated.

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