Skip to main content
Glama

remove_gear_from_activity

Destructive

Unlinks a specific gear item from a Garmin Connect activity using its activity ID and gear UUID to correct equipment associations.

Instructions

Remove gear association from an activity

    Unlinks a specific piece of gear from an activity.

    Args:
        activity_id: ID of the activity
        gear_uuid: UUID of the gear to remove
    

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": {
      "activity_id": "<activity_id>",
      "gear_uuid": "<gear_uuid>"
    },
    "name": "remove_gear_from_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
gear_uuidYes
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The unlink framing is consistent with annotations (readOnlyHint=false, destructiveHint=true) and adds the useful clarification that only the association is severed, not the gear or the activity itself. However, it says nothing about failure behavior when the gear is not linked, and nothing that explains the idempotentHint=false declaration, which an agent would want for retry logic.

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 purpose is front-loaded in the first line and the total length is small. The trailing Args block is largely redundant with the schema and could be dropped or used for genuinely new information.

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

Completeness3/5

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

For a simple two-parameter mutation with no output schema, this is roughly the minimum viable definition. Given destructiveHint=true and idempotentHint=false, a sentence on reversibility (re-add via add_gear_to_activity) and non-idempotent behavior would make it complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, but the Args block merely restates the schema titles ('ID of the activity', 'UUID of the gear to remove'). It adds no format detail, no constraint on where gear_uuid comes from (get_activity_gear vs get_gear), and no note that gear_uuid is a UUID string rather than an ID.

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?

The description states a specific verb and resource: 'Remove gear association from an activity' / 'Unlinks a specific piece of gear from an activity.' The remove/unlink framing naturally contrasts with the sibling add_gear_to_activity, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites (must the gear already be linked? must the activity exist?), and no mention of alternatives such as add_gear_to_activity or get_activity_gear. Usage is only inferable from the verb.

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