Skip to main content
Glama

get_activity_gear

Identify the gear used in a Garmin activity. Submit the activity ID to retrieve the equipment list.

Instructions

Get gear/equipment used during a specific activity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activityIdYesThe Garmin activity ID

Implementation Reference

  • Registration of the 'get_activity_gear' tool on the MCP server, including its description, input schema, and handler function that calls the client method.
    server.registerTool(
      'get_activity_gear',
      {
        description: 'Get gear/equipment used during a specific activity',
        inputSchema: getActivitySchema.shape,
      },
      async ({ activityId }) => {
        const data = await client.getActivityGear(activityId);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • The GarminClient method that executes the HTTP request to the Garmin API to fetch gear data for a given activity.
    async getActivityGear(activityId: number): Promise<unknown> {
      return this.request(`${ACTIVITY_GEAR_ENDPOINT}?activityId=${activityId}`);
    }
  • Zod schema defining the required input parameter 'activityId' (positive number) for the get_activity_gear tool.
    export const getActivitySchema = z.object({
      activityId: z.number().positive().describe('The Garmin activity ID'),
    });
  • API endpoint constant used by the client to construct the request URL for activity gear data.
    export const ACTIVITY_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. Description discloses basic read behavior (retrieves gear for an activity) but does not detail edge cases (e.g., empty results, errors, or performance).

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?

Single sentence, front-loaded verb and resource, no superfluous words. Excellent for a simple retrieval operation.

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 tool's simplicity (one required parameter, no output schema), the description sufficiently explains what the tool does. Slightly lower because the return shape is unspecified, but that's expected without an output schema.

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 provides full coverage (100%) for activityId with description 'The Garmin activity ID'. The tool description adds no further parameter context beyond what the schema already states.

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?

Description clearly states verb 'Get' and resource 'gear/equipment used during a specific activity'. It distinguishes from related tools like get_gear (general gear info) and get_gear_activities (gear-to-activity mapping).

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?

No explicit guidance on when to use this versus alternatives like get_gear or add_gear_to_activity. The context is implied but not stated.

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