Skip to main content
Glama
sedoglia

Garmin Connect MCP Server

by sedoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Earned Badges

get_earned_badges
Read-only

Retrieve all user-earned Garmin badges, showing category, difficulty, points, and earned date. Set includeDetails to get full badge records.

Instructions

Get all badges earned by the user, as id, key, name, category, difficulty, points and the date earned. 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

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint and openWorldHint, so the description does not need to repeat safety traits. It adds only the field list and a note about includeDetails, which is more about parameter semantics than behavior. This is acceptable but minimal, matching the baseline for read-only tools.

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 consists of two concise sentences: the first clearly states the purpose and returned fields, the second briefly notes the parameter effect. No filler or redundancy, and the main action is front-loaded.

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

Completeness5/5

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

The tool has only one optional parameter and no output schema, making it simple. The description covers the essential data returned and the parameter's effect, which combined with read-only annotations gives an agent sufficient information to invoke it correctly.

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 provides complete documentation for the single parameter includeDetails, including default behavior and response size implications. The description's mention of 'Set includeDetails for the full badge records' merely restates the schema without adding novel information. With 100% schema coverage, this is a baseline 3.

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?

The description clearly states the verb 'Get' and the resource 'all badges earned by the user', along with the specific fields returned. The word 'earned' differentiates it from related siblings like get_available_badges and get_in_progress_badges, though it does not explicitly name them.

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 is provided on when to use this tool versus alternatives such as get_available_badges or get_in_progress_badges. The distinction is only implied by the word 'earned', with no explicit recommendations or exclusions.

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