Skip to main content
Glama

get_earned_badges

Retrieve your complete collection of earned badges and achievements from Garmin Connect to track your progress and milestones.

Instructions

Get all earned badges and achievements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The anonymous handler function registered for the 'get_earned_badges' tool. Calls client.getEarnedBadges() and returns the result as JSON text.
    async () => {
      const data = await client.getEarnedBadges();
      return {
        content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
      };
    },
  • Registration of the 'get_earned_badges' tool on the MCP server via registerTool(), with description and handler.
    server.registerTool(
      'get_earned_badges',
      {
        description: 'Get all earned badges and achievements',
      },
      async () => {
        const data = await client.getEarnedBadges();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Client method that makes the API request to the Garmin Connect backend for earned badges.
    async getEarnedBadges(): Promise<unknown> {
      return this.request(EARNED_BADGES_ENDPOINT);
    }
  • Endpoint constant pointing to '/badge-service/badge/earned' for fetching earned badges from Garmin.
    export const EARNED_BADGES_ENDPOINT = '/badge-service/badge/earned';
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as authentication needs, rate limits, or whether it's a read-only operation. Minimal behavioral context beyond the basic action.

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?

One short sentence that is front-loaded with the verb and resource. No extraneous words, every word earns its place.

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?

For a zero-parameter retrieval tool, the description is minimally adequate. It explains what is returned but does not describe the output format, structure, or any limitations. Additional context about what 'achievements' entails would improve completeness.

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?

Input schema has zero parameters and 100% schema description coverage. Since there are no parameters to describe, the description adds no additional meaning, but the baseline for no parameters is 4.

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 'Get all earned badges and achievements', specifying the verb and resource. It distinguishes from sibling tools like get_available_badges and get_badge_challenges by focusing on 'earned' items.

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 when-to-use or when-not-to-use guidance. The name implies it's for earned badges versus available or challenges, but no alternative tools are mentioned. Usage 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