Skip to main content
Glama

remove_gear_from_activity

Unlink a gear item from a specific Garmin activity to correct gear associations and training logs.

Instructions

Unlink a gear item from an activity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gearUuidYesThe UUID of the gear item
activityIdYesThe Garmin activity ID

Implementation Reference

  • Client method that sends a PUT request to the gear unlink endpoint to remove a gear item from an activity.
    async removeGearFromActivity(gearUuid: string, activityId: number): Promise<unknown> {
      return this.request(
        `${GEAR_UNLINK_ENDPOINT}/${gearUuid}/activity/${activityId}`,
        { method: 'PUT' },
      );
    }
  • Zod schema for the gear activity input (gearUuid and activityId), used by remove_gear_from_activity.
    export const gearActivitySchema = z.object({
      gearUuid: z.string().uuid().describe('The UUID of the gear item'),
      activityId: z.number().positive().describe('The Garmin activity ID'),
    });
  • Tool registration for 'remove_gear_from_activity' with description, input schema, and handler callback.
    server.registerTool(
      'remove_gear_from_activity',
      {
        description: 'Unlink a gear item from an activity',
        inputSchema: gearActivitySchema.shape,
      },
      async ({ gearUuid, activityId }) => {
        const data = await client.removeGearFromActivity(gearUuid, activityId);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data ?? 'Gear unlinked', null, 2) }],
        };
      },
    );
  • Endpoint constant for the gear unlink API path used by removeGearFromActivity.
    export const GEAR_UNLINK_ENDPOINT = '/gear-service/gear/unlink';
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. 'Unlink' implies a write operation, but there is no disclosure of side effects, idempotency, or requirements like the gear item existing beforehand.

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?

A single, efficient sentence with no unnecessary words. Could be slightly expanded with usage context, but remains clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations or output schema, the description should mention that the gear must be linked, or the result type. It lacks this context, making it minimally complete.

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 covers both parameters with descriptions (gearUuid, activityId). The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 'Unlink a gear item from an activity' uses a specific verb ('Unlink') and resource ('gear item', 'activity'), clearly distinguishing it from siblings like 'add_gear_to_activity' 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?

No explicit guidance on when to use or alternatives. The purpose is implied but the description doesn't state prerequisites (e.g., gear must be currently linked) or contrast with 'add_gear_to_activity'.

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