Skip to main content
Glama

get_badge_challenges

Read-only

Retrieve completed Garmin badge challenges with earned dates, paginated by start and limit, to review achievement history.

Instructions

Get badge challenges the user has completed.

    Returns the completed badge-challenge history and earned dates. For
    challenges still in progress, use get_non_completed_badge_challenges.

    Args:
        start: Starting index for pagination (starts at 1)
        limit: Maximum number of challenges to return (default 20, max 100)
    

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_badge_challenges"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/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 by structured data. The description adds value beyond that by describing what comes back ('completed badge-challenge history and earned dates') and by disclosing pagination bounds, which matters because there is no output schema. It stops short of noting any auth, rate-limit, or ordering behavior, so it is strong but not maximal.

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?

The purpose sentence is front-loaded, followed by return/alternative guidance and a compact Args block. Every element carries information, though the 'Args:' section is a slightly mechanical format for only two well-understood parameters.

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 two-parameter read tool with no output schema, the definition covers purpose, return contents, alternative routing, and both parameter constraints. The absence of an output schema makes the brief return summary especially valuable. Missing only edge-case behavior (e.g., what an empty history returns or whether results are ordered by earned date), which keeps it from a 5.

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?

Schema description coverage is 0%, so the description must carry the parameter burden, and it largely does: start is documented as a 1-based pagination index and limit as a default-20, max-100 cap. These are exactly the non-obvious constraints (1-based indexing, upper bound) an agent would otherwise get wrong from the bare schema defaults. It does not explain what happens if limit exceeds 100 or how start interacts with the total count, keeping it out of the top band.

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?

States a specific verb and resource with an explicit scope qualifier: 'badge challenges the user has completed.' The 'completed' scope cleanly separates it from the sibling get_non_completed_badge_challenges, so an agent can pick the right tool without reading either schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative and the condition that selects it: 'For challenges still in progress, use get_non_completed_badge_challenges.' This is a direct when/when-not routing rule rather than an implied one, leaving nothing for the agent to guess.

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