Skip to main content
Glama

get_non_completed_badge_challenges

Read-only

Retrieve Garmin badge challenges you have joined but not completed. Use them to track progress toward badge goals.

Instructions

Get badge challenges currently in progress (not yet completed)

    Returns active challenges the user has joined but hasn't completed yet.
    Useful for tracking current progress toward badge goals.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/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 safety is covered. The description's real contribution is the filter semantics (joined but incomplete), which is genuinely behavioral, and the 'max 100' cap hints at server-side limits. It says nothing about result ordering or what happens at large offsets.

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 is front-loaded in the first line and the return shape follows immediately; the docstring-style 'Args:' block is functional rather than redundant. Minor waste in repeating that the function returns active challenges twice.

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-only listing tool with no output schema, the definition covers purpose, filter semantics, and both parameter meanings. Only the structure of individual returned challenges is left unstated, which is acceptable given no output schema was judged necessary.

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 carries the burden, and it does: 'start: Starting index for pagination (starts at 1)' and 'limit: Maximum number of challenges to return (default 20, max 100)' add the 1-based indexing and the upper bound that the bare schema does not state. Only the pagination behavior (e.g. is start an offset or page number) remains slightly ambiguous.

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 plus an explicit state qualifier: challenges 'currently in progress (not yet completed)' that the user has 'joined'. That state qualifier is what separates it from the sibling listing tools such as get_available_badge_challenges or get_badge_challenges, so an agent can pick correctly without opening a schema.

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?

'Useful for tracking current progress toward badge goals' gives a concrete use context, and the parenthetical 'not yet completed' implies when not to use it. It stops short of naming an alternative tool for completed or available challenges, so there is no explicit routing, but the usage framing is clear.

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