Skip to main content
Glama

get_gear

Retrieve all gear and equipment tracked in Garmin Connect, such as shoes and bikes.

Instructions

Get all gear/equipment: shoes, bikes, and other tracked equipment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler logic for 'get_gear' - calls the Garmin API endpoint to fetch all gear/equipment.
    async getGear(): Promise<unknown> {
      return this.request(`${GEAR_ENDPOINT}?userProfilePk=${this.userProfilePk}`);
    }
  • Registration of the 'get_gear' tool using McpServer.registerTool, with description and handler that calls client.getGear().
    server.registerTool(
      'get_gear',
      {
        description: 'Get all gear/equipment: shoes, bikes, and other tracked equipment',
      },
      async () => {
        const data = await client.getGear();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • The API endpoint constant used by getGear(): '/gear-service/gear/filterGear'
    export const GEAR_ENDPOINT = '/gear-service/gear/filterGear';
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It indicates a read operation ('Get'), which is adequate. However, it does not disclose any additional behavioral traits such as whether the response is paginated, what scope (e.g., user-specific) applies, or any rate limits. The description is minimal but sufficient for the tool's simplicity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that conveys the core functionality without any superfluous words. It is front-loaded with the action and resource, making it efficient and easy to parse.

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?

Given the low complexity (no parameters, no output schema), the description is mostly complete. It states what the tool returns (all gear/equipment) and provides examples. However, it could briefly mention the output format (e.g., list of gear objects) to be fully self-contained. Still, it is sufficient for an agent to understand and invoke the tool.

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?

The input schema has no parameters, and schema description coverage is 100% (vacuously). Per guidelines, with 0 parameters the baseline is 4. The description adds no parameter information because none is needed, but it does list example categories (shoes, bikes) which helps contextualize the result.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and the resource ('all gear/equipment'), listing examples like shoes, bikes, and other tracked equipment. It distinguishes from sibling tools such as get_gear_activities, get_gear_stats, and get_gear_defaults by covering the base list operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description implicitly conveys when to use this tool (to retrieve all gear) but does not explicitly state when not to use it or mention alternatives like get_gear_defaults. For a simple parameterless list tool, the context is clear enough, though explicit exclusions would improve it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nicolasvegam/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server