Skip to main content
Glama
sedoglia

Garmin Connect MCP Server

by sedoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Available Badges

get_available_badges
Read-only

Fetch all Garmin badges available to earn, including id, category, difficulty, points, and active window. Set includeDetails true to get complete badge records.

Instructions

Get all badges available to earn, as id, key, name, category, difficulty, points and, where set, the active window and progress. Set includeDetails for the full badge records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeDetailsNoReturn every field the badge service sends rather than the identifying ones (default false). This is a much larger response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.5.7
    • addedInput schema / properties / includeDetails
      Added value: +{
+  "description": "Return every field the badge service sends rather than the identifying ones (default false). This is a much larger response.",
+  "type": "boolean"
+}
  2. First observedv4.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint. The description adds useful behavioral context beyond those: it notes that active window and progress are returned only 'where set,' indicating optional fields, and it warns that includeDetails produces a much larger response. This helps an agent anticipate variability in output.

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?

Two focused sentences front-load the core purpose and return fields, then immediately handle the optional parameter. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with one optional parameter and no output schema, the description gives enough shape: it lists the returned fields and flags response-size behavior. It does not mention pagination or authentication, but the annotations and low parameter count make this a minor gap.

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?

The schema already describes includeDetails as returning every field (default false) and notes the response is much larger. The description's 'full badge records' adds little beyond the schema's own coverage, so the baseline of 3 applies.

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 uses a specific verb and resource ('Get all badges available to earn') and lists the exact fields returned. This clearly distinguishes the tool from siblings like get_earned_badges and get_in_progress_badges by emphasizing 'available to earn' versus earned or in-progress states.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool: to list badges that can be earned. It does not explicitly name alternatives or exclusion criteria, but the phrase 'available to earn' implicitly separates it from earned-badge and challenge tools. It also gives usage guidance for the includeDetails parameter.

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