Skip to main content
Glama

get_available_badges

Retrieve a list of all badges you can earn through Garmin Connect activities and challenges.

Instructions

Get all available badges that can be earned

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool 'get_available_badges' is registered with the MCP server via 'registerTool' with a description.
    server.registerTool(
      'get_available_badges',
      {
        description: 'Get all available badges that can be earned',
      },
      async () => {
        const data = await client.getAvailableBadges();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Handler method 'getAvailableBadges' on GarminClient makes the actual API request to the badges endpoint.
    async getAvailableBadges(): Promise<unknown> {
      return this.request(AVAILABLE_BADGES_ENDPOINT);
    }
  • Endpoint constant pointing to '/badge-service/badge/available'.
    export const AVAILABLE_BADGES_ENDPOINT = '/badge-service/badge/available';
Behavior3/5

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

No annotations provided, so the description carries full burden. It correctly indicates a read operation but does not disclose any limitations, authentication needs, or output format. Acceptable but minimal.

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 eight-word sentence, front-loaded with purpose. No redundant or unnecessary information. Highly efficient.

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 no parameters and no output schema, description is somewhat incomplete. It does not explain what 'available' means or whether the list is filtered by user. Adequate for a simple retrieval but could be clearer.

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?

No parameters in schema, so schema coverage is 100%. Baseline is 3; description adds no param info because none exist. Adequate.

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) and the resource (all available badges that can be earned). It effectively distinguishes from sibling tools like get_earned_badges and get_non_completed_badge_challenges by emphasizing 'available' and 'can be earned'.

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 on when to use this tool versus alternatives. With many sibling tools (e.g., get_earned_badges, get_adhoc_challenges), the description should clarify context but does not.

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