Skip to main content
Glama

get-badges

Access all earned badges and achievements from your Garmin Connect account.

Instructions

Get all earned badges/achievements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.ts:656-665 (registration)
    Registration of the 'get-badges' tool via server.tool() - defines name, description, schema (empty), and handler
    server.tool(
      "get-badges",
      "Get all earned badges/achievements",
      {},
      async () => {
        const client = getClient();
        const data = await client.get("badge-service/badge/earned");
        return jsonResult(data);
      }
    );
  • Handler function for 'get-badges': calls badge-service/badge/earned endpoint and returns JSON result
    async () => {
      const client = getClient();
      const data = await client.get("badge-service/badge/earned");
      return jsonResult(data);
    }
  • jsonResult helper used to format the API response as text content
    function jsonResult(data: unknown) {
      return {
        content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }],
      };
    }
  • Imports getSharedClient (as getClient) from garmin-client, used to make the API call
      getSharedClient,
      resetSharedClient,
      sessionExists,
      getSessionFile,
    } from "./garmin-client.js";
  • src/test.ts:467-473 (registration)
    Test for 'get-badges' tool calling it and checking for errors
    {
      name: "get-badges",
      run: async (server) => {
        const result = await callTool(server, "get-badges");
        if (result.isError) throw new Error(getToolText(result));
      },
    },
Behavior2/5

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

No annotations are provided, and the description offers no details about behavioral traits such as authentication requirements, rate limits, or side effects. It only states the basic functionality, leaving the agent with minimal 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, clear sentence with no unnecessary words. It is appropriately front-loaded and concise.

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 tool's simplicity (no parameters, no output schema), the description provides the core purpose. However, it does not specify the return format or what constitutes 'earned' badges, leaving some ambiguity. Adequate but could be improved.

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?

The input schema has zero parameters and 100% coverage. The description adds no parameter information, which is acceptable since there are none. Baseline 4 is appropriate for a parameterless tool.

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 verb 'Get' and resource 'all earned badges/achievements', distinguishing it from the sibling tool 'get-badge-leaderboard' which gets leaderboard data.

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 for retrieving earned badges, but provides no explicit guidance on when to use this tool versus alternatives or any exclusions. However, with zero parameters and clear purpose, the implied usage is adequate.

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/etweisberg/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server