Skip to main content
Glama

get_gear_defaults

Get default gear assignments for each activity type to know which equipment is automatically associated with your workouts.

Instructions

Get default gear assignments per activity type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'get_gear_defaults' tool on the MCP server. It has a description 'Get default gear assignments per activity type' and calls client.getGearDefaults().
    server.registerTool(
      'get_gear_defaults',
      {
        description: 'Get default gear assignments per activity type',
      },
      async () => {
        const data = await client.getGearDefaults();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Handler function getGearDefaults() that calls this.request() with the GEAR_DEFAULTS_ENDPOINT URL plus userProfilePk and '/activityTypes'.
    async getGearDefaults(): Promise<unknown> {
      return this.request(`${GEAR_DEFAULTS_ENDPOINT}/${this.userProfilePk}/activityTypes`);
    }
  • Constant GEAR_DEFAULTS_ENDPOINT = '/gear-service/gear/user' used to construct the API request URL.
    export const GEAR_DEFAULTS_ENDPOINT = '/gear-service/gear/user';
  • Helper getter userProfilePk that retrieves the user's profile primary key from auth, used in building the request URL.
    private get userProfilePk(): number {
      return this.auth.userProfilePk;
    }
  • The userProfilePk getter on GarminAuth returns the profileId from the user profile.
    get userProfilePk(): number {
      return this.profile?.profileId ?? 0;
    }
Behavior2/5

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

Annotations are absent, so the description carries the full burden. It only states the function, without mentioning that it is a read-only operation, what the output format is, or any permissions needed. Minimal disclosure for a tool with no additional behavioral cues.

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 clear sentence with no extraneous words. It is well-structured and front-loaded, efficiently conveying the core function.

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?

Given the tool's simplicity (no parameters, no output schema), the description is adequate but incomplete. It does not hint at the output structure (e.g., a mapping of activity types to gear IDs) or mention if it returns all activity types or only those with defaults. More context would improve completeness.

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 tool has zero parameters, so the schema provides full coverage. The description does not add value beyond the schema, but a baseline of 4 is appropriate given the absence of parameters. No further clarification is needed.

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 tool retrieves default gear assignments per activity type, using a specific verb ('get') and resource. It distinguishes itself from siblings like 'get_gear' and 'add_gear_to_activity', which deal with different aspects of gear management.

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 is provided on when to use this tool versus alternatives. For example, it does not contrast with 'get_gear' or 'get_activity_gear' to clarify its specific role. The description lacks when-to-use and when-not-to-use information.

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