Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_inprogress_virtual_challenges

Read-only

Retrieve Garmin Connect virtual challenges that are currently in progress, using start and limit for pagination.

Instructions

Virtual challenges in progress. start must be at least 1. GETs /badgechallenge-service/virtualChallenge/inProgress; asymmetric validation: start validated POSITIVE here (rejects start=0), unlike the non-negative start on the four challenge methods above; limit validated positive; same array-not-dict correction.

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

Input Schema

NameRequiredDescriptionDefault
limitYes
startYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnlyHint/openWorldHint, but the description adds real behavioral value: the asymmetric validation (start validated positive here, rejecting start=0, unlike the non-negative start elsewhere), positive limit validation, and the 'array-not-dict' correction. This is meaningful disclosure beyond the 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the body is dense with cross-references ('the four challenge methods above', 'same array-not-dict correction') that point at context not present in this definition and can confuse an isolated reader. The critical start constraint is buried mid-sentence.

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 two-parameter read-only list tool with no output schema, the description covers the key behavioral quirks (validation asymmetry, response shape) but omits any sense of what the returned virtual challenges contain or pagination behavior. Adequate but with clear gaps.

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 carries the full burden and largely meets it: it documents that start must be at least 1 (rejecting 0) and that limit is validated positive. It does not explain the offset/limit pagination semantics of start itself, but the validation constraints are precisely specified.

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 states the specific resource ('Virtual challenges in progress') and implies the list/get verb, and it situates itself in the challenge family by referencing 'the four challenge methods above.' It stops short of naming the sibling that retrieves a different challenge state, so an agent must infer the distinction rather than being told it.

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' scope implicitly indicates when this applies versus available/earned/completed challenges, and it references the other challenge methods. However, there is no explicit 'use this when / not when' routing or named alternative, so usage is only implied.

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