Skip to main content
Glama

add_gear_to_activity

Links a specific gear item, such as shoes or a bike, to a Garmin activity using the activity ID and gear UUID.

Instructions

Associate gear with an activity

    Links a specific piece of gear (like shoes, bike, etc.) to an activity.

    Args:
        activity_id: ID of the activity
        gear_uuid: UUID of the gear to add (get from get_gear)
    

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": "add_gear_to_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
gear_uuidYes
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the mutation profile is covered. The description adds nothing beyond that: it does not say what happens if the gear is already attached, whether the call duplicates the link (relevant given idempotentHint=false), or what the response contains.

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?

Front-loaded one-line summary followed by a clarifying sentence and a short Args block — nothing extraneous. The Args section largely restates schema property names, which is mild redundancy, but the overall size is appropriate for a two-parameter tool.

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, the description covers purpose and both parameters, which is close to sufficient. It falls short on mutation-side behavior — duplicate handling and success/failure semantics — which matters for a non-idempotent write.

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 description coverage is 0%, so the description must carry the parameter burden and it largely does: activity_id is identified as the activity's ID and gear_uuid as the gear's UUID, with an explicit pointer to get_gear as the source. What is missing is whether activity_id is the numeric Strava-style activity ID versus another identifier form.

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 gives a specific verb plus resource: "Associate gear with an activity" / "Links a specific piece of gear (like shoes, bike, etc.) to an activity." The direction of the association (add rather than remove) is unambiguous, which implicitly separates it from remove_gear_from_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 Guidelines3/5

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

Usage is implied by the operation itself, and the parenthetical "get from get_gear" is a genuine routing hint to the sibling that supplies the gear_uuid. However, there is no statement of when to prefer this over alternatives, nor any prerequisites (e.g. gear must exist, activity must be owned by the caller).

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