Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

set_gear_activity_defaults

Destructive

Set or clear which Garmin Connect activity types default to a specific gear. Confirm before calling because this change is irreversible.

Instructions

Sets which activity types default to this gear. Uses the v2 full-record PUT Garmin's own web client uses (the older dedicated default-gear endpoint is dead). The working way to set gear defaults (the old dedicated default-gear endpoint is dead; there is no setGearDefault). Read-modify-writes the v2 record: GETs /gear-service/gear/v2/{uuid}, replaces associatedActivityTypes with [{activityTypeKey, defaultGear: true, preferredGear: false}] per key, PUTs the whole record back. Keys are lowercase ("running"), matching createGear, NOT setGearDefault's upper-cased form. [] clear… 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>",
      "activityTypeKeys": "<activityTypeKeys>"
    },
    "name": "set_gear_activity_defaults"
  }
}

Input Schema

NameRequiredDescriptionDefault
gearUUIDYes
activityTypeKeysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantive behavior beyond them: it is a read-modify-write of the whole v2 record, existing associatedActivityTypes are replaced, and the operation is irreversible. The GET/replace/PUT sequence is exactly the kind of context annotations cannot convey.

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

Conciseness3/5

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

Purpose is front-loaded, but the text is repetitive: the 'old dedicated default-gear endpoint is dead' claim appears twice and there is tangential API lore. Sentences are dense with useful content but could be tightened by roughly a third without losing meaning.

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?

For a destructive, zero-schema-coverage mutation with no output schema, the description supplies the essential context: irreversibility, the read-modify-write nature, key casing, and the clear semantics. The only real gap is what gearUUID refers to and any permission requirements.

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?

Schema coverage is 0%, so the description must carry the parameters, and it does: it specifies activityTypeKeys must be lowercase ('running'), matching createGear and not the upper-cased setGearDefault form, and that '[]' clears the defaults. gearUUID is only implied by the GET path, so it is not a full 5.

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: 'Sets which activity types default to this gear.' It goes further by naming the mechanism and contrasting with related operations (createGear, the dead setGearDefault), which helps the agent place it among gear tools. Not a 5 because the purpose statement is muddied by repetitive endpoint lore rather than a crisp one-line summary.

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?

Provides a real usage cue: 'IRREVERSIBLE: confirm with the user before calling.' That is genuine when-to-act guidance. However it gives no explicit routing against alternatives (e.g. add_gear_to_activity vs this), only a safety precondition, so it lands at minimum-viable-plus.

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