Skip to main content
Glama

get_earned_badges

Read-only

Retrieve the badges a Garmin Connect user has earned, so you can review achievements and track completed challenges.

Instructions

Get earned badges for user

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_earned_badges"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it doesn't say whether "user" means the authenticated user, whether results are paginated, or how far back earned badges are reported. For an open-world read with zero added context, this is a meaningful gap.

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 short sentence with no filler; nothing is wasted. It is arguably over-compressed, but the structure is front-loaded and readable.

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?

With zero parameters, no output schema, and annotations covering the read-only profile, a short description is defensible. Still, the definition leaves open whose badges are returned and what the response contains, which an agent would want to know before calling it.

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 tool takes no parameters, so the baseline is 4; the description has no parameter semantics to explain and none are needed. The phrase "for user" hints the target user is implicit from auth context, though the description never states this explicitly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get earned badges for user" states a specific verb (get) and resource (earned badges), which is clearly distinct from fetching activities or challenges. However, it does not differentiate itself from the nearby badge-related siblings (e.g., get_badge_challenges, get_available_badge_challenges), so an agent must infer that this tool returns already-earned badges only.

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?

The description gives no guidance on when to use this tool rather than the badge/challenge siblings, nor any prerequisites (e.g., whether authentication is required or whose badges are returned). Usage must be guessed purely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools