Skip to main content
Glama

get_gear

Read-only

Retrieve all gear registered to a Garmin account, including usage statistics, notes, and default activity associations; disable stats for faster responses with large gear collections.

Instructions

Get all gear registered with the user account

    Returns complete gear inventory including free-text notes, usage statistics,
    and default activity associations. The notes field is null when unavailable.
    defaults maps each activity type (Garmin typeKey, e.g. "running") to the
    names of its default gear.
    A gear item's stats_error reports a failed usage-statistics request;
    a null total_distance_km means Garmin did not provide a distance.
    No parameters required - user profile is fetched automatically.

    Args:
        include_stats: Include usage statistics for each gear item (default True).
                       Set to False for faster response with large gear collections.
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_gear"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_statsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), yet the description adds real behavioral context: what the response contains, that notes is null when unavailable, that stats_error signals a failed statistics request, and that a null total_distance_km means Garmin omitted distance. It does not mention auth scopes or rate limits, keeping it short of a 5.

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 lead sentence is front-loaded and each subsequent sentence explains a distinct field or edge case rather than restating. The trailing 'Args:' docstring block is slightly redundant with the schema but stays tight and earns its place.

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?

With one optional parameter, no output schema, and annotations covering safety, the description supplies what an agent needs: the response shape, the null semantics, the defaults mapping, and the cost tradeoff of the single flag. The only gap is the absence of any pointer distinguishing this from the activity-level gear siblings.

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, and it does: include_stats is documented with its default (True) and the operational reason to set it False for faster responses on large gear collections. That is meaningful guidance beyond the bare boolean in the schema.

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: 'Get all gear registered with the user account,' and the following sentences clarify that this is the complete inventory with defaults and per-item stats. It never names get_activity_gear or explains the difference from the activity-scoped gear siblings, so the boundary must be inferred.

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 only implied — 'No parameters required - user profile is fetched automatically' tells the agent no setup is needed, and the include_stats note gives a tradeoff for large collections. There is no explicit when-to-use statement and no routing to or exclusion of the sibling tools that also touch gear.

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