Skip to main content
Glama

get_badge_challenges

Retrieve a list of completed badge challenges from your Garmin Connect account.

Instructions

Get completed badge challenges

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'get_badge_challenges' tool via server.registerTool, with description 'Get completed badge challenges' and a handler that calls client.getBadgeChallenges().
    server.registerTool(
      'get_badge_challenges',
      {
        description: 'Get completed badge challenges',
      },
      async () => {
        const data = await client.getBadgeChallenges();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Handler function getBadgeChallenges() in GarminClient class that executes the API request to the badge challenges endpoint.
    async getBadgeChallenges(): Promise<unknown> {
      return this.request(BADGE_CHALLENGES_ENDPOINT);
    }
  • Endpoint constant BADGE_CHALLENGES_ENDPOINT defining the API URL path for completed badge challenges.
    export const BADGE_CHALLENGES_ENDPOINT = '/badgechallenge-service/badgeChallenge/completed';
    export const AVAILABLE_BADGE_CHALLENGES_ENDPOINT = '/badgechallenge-service/badgeChallenge/available';
    export const NON_COMPLETED_BADGE_CHALLENGES_ENDPOINT = '/badgechallenge-service/badgeChallenge/non-completed';
  • Import and usage of the BADGE_CHALLENGES_ENDPOINT constant in the client imports.
    BADGE_CHALLENGES_ENDPOINT,
    AVAILABLE_BADGE_CHALLENGES_ENDPOINT,
    NON_COMPLETED_BADGE_CHALLENGES_ENDPOINT,
    INPROGRESS_VIRTUAL_CHALLENGES_ENDPOINT,
Behavior3/5

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

With no annotations, the description does not disclose any behavioral traits such as return format, authorization needs, or side effects. It merely states the action without additional context.

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 is concise and front-loaded, effectively conveying the tool's purpose without unnecessary words.

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 complexity (zero parameters, no output schema), the description is minimal but adequate. It lacks details about what constitutes a 'completed badge challenge' or the response structure.

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?

There are no parameters, so baseline 4 applies. The description adds no extra meaning beyond the schema, but no additional information 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 'Get completed badge challenges' uses a specific verb and resource, clearly distinguishing it from sibling tools like get_available_badge_challenges and get_non_completed_badge_challenges.

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 guidelines on when to use this tool versus alternatives. The purpose implies it is for retrieving completed challenges, but no direct comparison or caveats 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