Skip to main content
Glama

get_adhoc_challenges

Read-only

Retrieve user-created social and group challenges, such as step competitions with friends, to track and compare progress separately from official Garmin badge challenges.

Instructions

Get user-created social/group challenges (e.g., step competitions with friends)

    Returns challenges created by users to compete with connections. These are
    different from official Garmin badge challenges.

    Args:
        start: Starting index for pagination (default 0)
        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_adhoc_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 the safety profile is covered. The description adds the useful content-level fact that these are user-created challenges distinct from official badges, but says nothing about return shape, ordering, or what an empty result looks like. With annotations carrying the behavioral burden, this is adequate but not rich.

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 Args block is easy to scan. There is mild redundancy between "Get user-created social/group challenges" and "Returns challenges created by users," but every other sentence carries distinct information and nothing is padded.

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?

This is a simple two-parameter read-only list tool with no output schema, so the description needs only purpose, disambiguation, and parameter meaning, all of which are present. The remaining gap is minor: no note on result ordering or whether pagination terminates.

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 coverage is 0%, so the description must carry parameter meaning, and it does: start is documented as the starting index for pagination with default 0, and limit as the maximum number to return with default 20. It also contributes the max of 100 for limit, which does not appear anywhere in the schema.

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 names a specific verb and resource ("Get user-created social/group challenges") and immediately disambiguates with a concrete example ("step competitions with friends"). It explicitly separates itself from official Garmin badge challenges, which is the key distinction against siblings like get_badge_challenges and get_available_badge_challenges.

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?

It gives clear context for when this tool is the right one: user-created social/group challenges rather than official badge challenges. It does not explicitly name an alternative tool to use instead, but the exclusion of official badge challenges is stated directly, which is enough for correct selection.

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