garminconnect-js

get_gear_activities

Read-only

Retrieve activities associated with a specific piece of gear by its UUID, with an optional limit up to 1000; returns an empty list if the gear is unknown.

Instructions

Activities that used a piece of gear (limit capped at 1000); [] if it is unknown. limit clamped to 1000; returns [] on a 404 instead of throwing.

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>"
    },
    "name": "get_gear_activities"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`gearUUID`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

B3.4/5.0

Behavior4/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 genuine value beyond that: limit is clamped/capped at 1000, returns [] for unknown gear, and returns [] on a 404 instead of throwing. This error-handling and edge-case disclosure is exactly what annotations don't provide.

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?

Very short and front-loaded, leading with what is returned. The 1000 cap is stated three times ('capped at 1000', 'clamped to 1000'), which is minor redundancy but doesn't obscure the content.

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?

There is no output schema, so the description should ideally convey the return shape, which it does not beyond '[]'. Error handling is well covered, but pagination semantics (limit without offset) and returned fields are left unstated for a tool whose only output documentation is the empty-array case.

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 0%, so the description must carry the load. It meaningfully documents `limit` (clamped at 1000) but only implicitly identifies `gearUUID` via 'a piece of gear', adding no format or source detail. Partial compensation for the coverage gap, so a mid score.

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 resource and relation: 'Activities that used a piece of gear'. An agent can tell this returns activities, not gear metadata. However it doesn't distinguish itself from close siblings like get_gear, get_gear_stats, or get_activity_gear, which could be confused for the same purpose.

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 guidance on when to call this versus get_gear_stats, get_gear, or get_activity_gear. The only usage-flavored hint is the 404 behavior, which describes runtime behavior rather than selection criteria. The agent must infer usage from the name alone.

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

Deploy Server