garminconnect-js

get_available_badge_challenges

Read-only

Retrieve Garmin badge challenges the account can join, using paginated results that start at 1 to avoid the 400 error caused by start=0.

Instructions

Badge challenges the account can join. Garmin rejects start=0; start at 1. GETs /badgechallenge-service/badgeChallenge/available; same start/limit validation; same array-not-dict correction and same live start=0 -> 400 discovery as getBadgeChallenges.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start": "<start>",
      "limit": "<limit>"
    },
    "name": "get_available_badge_challenges"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	Yes
`start`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds meaningful non-obvious behavior: Garmin rejects `start=0`, the endpoint path, the array-not-dict correction, and the live 400 discovery. These are real behavioral traits an agent can't infer from structured fields.

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?

Purpose is front-loaded in the first clause, followed by dense implementation notes. Very compact for the amount of quirk detail conveyed, though the backward references to `getBadgeChallenges` assume the reader has already seen that definition.

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 read-only list endpoint with no output schema, the description covers the pagination traps well but says nothing about the shape or fields of returned challenges, leaving a gap for an agent that needs to interpret results.

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?

Schema coverage is 0%, so the description must carry the burden. It does add one key constraint — `start` must begin at 1, not 0 — but defers the rest to 'same `start`/`limit` validation' without stating the limit range or defaults, leaving meaning partially implied.

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?

States the resource and scope precisely: 'Badge challenges the account can join,' which distinguishes the joinable set from earned/in-progress siblings. It references `getBadgeChallenges` for parity rather than explicitly differentiating from other badge siblings like `get_available_badges`, but the verb+resource is clear.

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 explicit guidance on when to use this tool versus alternatives such as `get_badge_challenges`, `get_available_badges`, or `get_non_completed_badge_challenges`. Comparisons to `getBadgeChallenges` are about implementation quirks, not selection criteria.

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

Deploy Server