garminconnect-js

get_activity_gear

Read-only

Retrieve the gear linked to a specific Garmin Connect activity by providing its activity ID. Returns an array of associated gear for that activity.

Instructions

The gear linked to an activity. Returns an ARRAY, verified live.

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

Input Schema

Name	Required	Description	Default
`activityId`	Yes	Numeric id

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one useful piece of behavior beyond annotations: it returns an ARRAY (compensating for the absent output schema). 'Verified live' is testing provenance rather than agent-relevant behavior, and nothing is said about empty results when no gear is linked.

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?

Two short sentences, front-loaded with the purpose and the return shape. The trailing 'verified live' phrase is meta-commentary that consumes space without informing an agent's invocation decision.

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?

With no output schema, the description carries the burden of describing returns and does only the minimum: it says an ARRAY comes back but never what each element contains or how empty results appear. For a simple single-parameter read this is adequate but leaves a real gap on the return contract.

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 coverage is 100%, with activityId documented as 'Numeric id' and constrained to the single required parameter. The description adds no format details, id source, or the fact that the field also accepts a string despite the 'Numeric' label. Baseline 3 is appropriate when the schema carries parameter documentation.

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 names the exact resource and its relationship: gear linked to a specific activity, which is distinct from get_gear (gear inventory) and get_gear_activities (activities for gear). It is clear, but it never names or contrasts those siblings, so the agent must infer the distinction from the name alone.

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?

No when-to-use guidance and no mention of the closely related get_gear, get_gear_activities, or add_gear_to_activity tools. The agent gets no signal about when this lookup is preferable to the other gear endpoints in the sibling list.

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

Deploy Server