Skip to main content
Glama

get_gear_activities

Get a list of activities associated with a specific gear item, like runs using a particular pair of shoes. Paginate results with offset and limit parameters.

Instructions

Get activities associated with a specific gear item (e.g. runs with a specific pair of shoes)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gearUuidYesThe UUID of the gear item
startNoPagination offset. Defaults to 0
limitNoNumber of activities to return (1-100). Defaults to 20

Implementation Reference

  • The client method that executes the API request for gear activities. Calls the Garmin endpoint '/activitylist-service/activities/{gearUuid}/gear' with pagination params.
    async getGearActivities(gearUuid: string, start = 0, limit = DEFAULT_GEAR_ACTIVITIES_LIMIT): Promise<unknown> {
      return this.request(`${GEAR_ACTIVITIES_ENDPOINT}/${gearUuid}/gear?start=${start}&limit=${limit}`);
    }
  • Zod schema and TypeScript type for the 'get_gear_activities' tool input (gearUuid, start, limit).
    export const getGearActivitiesSchema = z.object({
      gearUuid: z.string().uuid().describe('The UUID of the gear item'),
      start: z
        .number()
        .min(0)
        .default(0)
        .optional()
        .describe('Pagination offset. Defaults to 0'),
      limit: z
        .number()
        .min(1)
        .max(100)
        .default(20)
        .optional()
        .describe('Number of activities to return (1-100). Defaults to 20'),
    });
  • Registration of the 'get_gear_activities' tool on the MCP server with description, input schema, and handler callback.
    server.registerTool(
      'get_gear_activities',
      {
        description: 'Get activities associated with a specific gear item (e.g. runs with a specific pair of shoes)',
        inputSchema: getGearActivitiesSchema.shape,
      },
      async ({ gearUuid, start, limit }) => {
        const data = await client.getGearActivities(gearUuid, start ?? 0, limit ?? 20);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Import of getGearActivitiesSchema and the registerProfileTools function that registers the tool.
    import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
    import { GarminClient } from '../client';
    import {
      getDeviceSettingsSchema,
      getDeviceSolarSchema,
      getGearStatsSchema,
      getGearActivitiesSchema,
      getWorkoutSchema,
    } from '../dtos';
    
    export function registerProfileTools(server: McpServer, client: GarminClient): void {
  • The API endpoint constant GEAR_ACTIVITIES_ENDPOINT used by the client to fetch gear activities.
    export const GEAR_ACTIVITIES_ENDPOINT = '/activitylist-service/activities';
Behavior3/5

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

No annotations are present, so the description carries the burden. It indicates a read operation but does not mention pagination (though params imply it), error handling, or behavior when no activities exist. Adequate for a simple retrieval tool.

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 with a concrete example, front-loading the core purpose. No unnecessary words.

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?

For a simple retrieval tool with three parameters (one required), the description is mostly complete. It lacks details on return format and error conditions, but these are common gaps. The pagination is handled by 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?

The input schema has 100% description coverage, so baseline is 3. The description adds an illustrative example (sneakers) but no additional semantic detail beyond the schema.

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 action ('Get'), the resource ('activities'), and the context ('associated with a specific gear item'). It provides an example ('runs with a specific pair of shoes'), which differentiates it from siblings like 'get_activities' and 'get_activity_gear'.

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?

The description implies usage when needing activities for a gear item but does not explicitly state when to use it versus alternatives (e.g., 'get_activity_gear' for the reverse). No exclusions or prerequisites are provided.

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