Skip to main content
Glama

get_inprogress_virtual_challenges

Read-only

Retrieve in-progress virtual challenges and walking expeditions a Garmin Connect user is currently participating in, with start and limit parameters for pagination.

Instructions

Get in-progress virtual challenges/expeditions

    Returns virtual challenges (like walking expeditions on famous trails)
    that the user is currently participating in.

    Args:
        start: Starting index for pagination (default 1, must be >= 1;
            garminconnect 0.3.2 rejects 0 for this endpoint)
        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_inprogress_virtual_challenges"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 safety is covered. The description adds genuine behavioral context beyond that: the underlying client library (garminconnect 0.3.2) rejects start=0 for this specific endpoint, and that the result set is limited to what the user is actively enrolled in.

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 line, followed by a one-sentence elaboration and a compact Args block. The 'Args:' docstring formatting is slightly mechanical for a tool description and the '>= 1' / 'rejects 0' statements overlap, but nothing is wasted.

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 list tool with no output schema, this covers what is returned, who the results belong to, and how to page through them. A brief note on whether an empty list versus an error occurs when the user has no active challenges would make it fully complete.

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 full burden and mostly does: it restates both parameters with defaults, adds the non-obvious lower bound ('must be >= 1'), explains the library-level reason 0 fails, and supplies a max of 100 that the schema does not declare. The only gap is that the schema's lack of an upper bound on 'start' is not discussed further.

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 names a specific verb and resource ('Get in-progress virtual challenges/expeditions') and clarifies the domain with a concrete example ('walking expeditions on famous trails'). It also narrows scope to challenges 'the user is currently participating in', which separates it from the available/completed style siblings, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

The 'in-progress' qualifier implies when to call this rather than a badge or available-challenge tool, but there is no explicit when-to-use/when-not-to-use statement and no named alternative. An agent must infer the routing from the adjective alone.

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