Skip to main content
Glama
sedoglia

Garmin Connect MCP Server

by sedoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update Gear

update_gear
Destructive

Update existing gear details such as brand, model, display name, or replacement distance. Use gear UUID from get_all_gear to modify equipment information.

Instructions

Update existing gear/equipment details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gearUUIDYesThe gear UUID (use get_all_gear to find it) (required)
brandNameNoBrand name. Garmin keeps brand and model as one free-text label, so this is combined with modelName.
modelNameNoModel name. Garmin keeps brand and model as one free-text label, so this is combined with brandName.
displayNameNoNew display name
maximumMeterNoMaximum distance in meters before replacement

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.5.7
    • changedInput schema / properties / brandName / description
      Previous value: -"New brand name"New value: +"Brand name. Garmin keeps brand and model as one free-text label, so this is combined with modelName."
    • changedInput schema / properties / modelName / description
      Previous value: -"New model name"New value: +"Model name. Garmin keeps brand and model as one free-text label, so this is combined with brandName."
  2. First observedv4.3.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this is a mutating operation. The description adds no additional behavioral context—no mention of side effects, partial update semantics, or impact on linked activities.

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 description is a single front-loaded sentence with no wasted text. It is concise and readable, though it is also sparse and does not add much information beyond the tool name.

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 destructive update tool with five parameters and no output schema, the description is minimal. The schema covers parameter semantics and annotations cover the safety profile, but the description does not explain update semantics or prerequisites beyond what is already in the schema.

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 100%, so the schema fully documents all five parameters, including the combined brand/model behavior. The description itself adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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 uses a specific verb ('Update') and resource ('existing gear/equipment details'), making the action unambiguous. It is clearly distinct from read tools like get_all_gear and destructive tools like delete_gear, though it does not explicitly name sibling alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives such as delete_gear or get_all_gear. The only usage hint ('use get_all_gear to find it') appears in the schema's gearUUID parameter description, not in the tool description itself.

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