garminconnect-js

remove_gear_from_activity

Unlinks gear from a Garmin activity using the gear UUID and activity ID. Use when a piece of equipment is incorrectly associated with an activity.

Instructions

Unlinks a piece of gear from an activity. PUT, not DELETE; same 404-handling pattern as addGearToActivity.

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>",
      "activityId": "<activityId>"
    },
    "name": "remove_gear_from_activity"
  }
}

Input Schema

Name	Required	Description	Default
`gearUUID`	Yes
`activityId`	Yes	Numeric id

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already disclose readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds genuinely new behavioral context beyond that: the HTTP method is PUT rather than DELETE, and it inherits a 404-handling pattern from the sibling — both useful for an agent anticipating error behavior.

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?

Two short sentences with zero filler; the core action is front-loaded and the method/error nuance follows. Every clause earns its place.

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?

No output schema, but annotations cover the safety profile, and the description adds the method and error-handling pattern. What remains thin is per-parameter meaning, which leaves the definition slightly incomplete for a 2-required-param mutation tool.

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 only 50% (activityId is documented as "Numeric id", gearUUID has nothing), and the description never mentions either parameter, so it does not compensate for the gap. Names are self-explanatory, keeping this at the minimum-viable baseline rather than below it.

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 uses a specific verb ("Unlinks") plus the exact resource boundary ("a piece of gear from an activity"), which is unambiguous and clearly the inverse of the sibling `add_gear_to_activity`. An agent can distinguish it from delete_gear or set_gear_activity_defaults 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 Guidelines3/5

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

Usage is implied by naming the counterpart operation (`addGearToActivity`), so the agent can infer this is the removal path. However, there is no explicit statement of when to use this versus alternatives like `delete_gear`, nor any prerequisite conditions.

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

Deploy Server