Skip to main content
Glama

get_inprogress_virtual_challenges

Fetch all virtual challenges currently in progress. Stay updated on active fitness challenges.

Instructions

Get virtual challenges currently in progress

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Client method that makes the HTTP request to fetch in-progress virtual challenges from the Garmin API endpoint.
    async getInProgressVirtualChallenges(): Promise<unknown> {
      return this.request(INPROGRESS_VIRTUAL_CHALLENGES_ENDPOINT);
    }
  • Registers the 'get_inprogress_virtual_challenges' tool on the MCP server, calling the client method and returning JSON.
    server.registerTool(
      'get_inprogress_virtual_challenges',
      {
        description: 'Get virtual challenges currently in progress',
      },
      async () => {
        const data = await client.getInProgressVirtualChallenges();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Schema/description for the tool: no input parameters, description 'Get virtual challenges currently in progress'.
    'get_inprogress_virtual_challenges',
    {
      description: 'Get virtual challenges currently in progress',
  • Endpoint constant pointing to '/badgechallenge-service/virtualChallenge/inProgress' used by the client handler.
    export const INPROGRESS_VIRTUAL_CHALLENGES_ENDPOINT = '/badgechallenge-service/virtualChallenge/inProgress';
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits like authorization requirements, whether results are user-specific, or what defines 'in progress'. The description is minimal and relies entirely on the tool name.

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 description is a single, concise sentence that is front-loaded with the verb and resource. It is appropriately brief but could be slightly restructured to front-load the core action even more.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and the presence of many sibling challenge tools, the description is insufficient. It fails to explain the return format, how 'in progress' is determined, or whether the tool requires specific permissions.

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?

There are no parameters in the input schema, so baseline is 4. The description adds value by implying a temporal filter ('currently in progress'), which gives context beyond the empty 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 'Get virtual challenges currently in progress' clearly identifies the action (get) and the specific resource (virtual challenges in progress), distinguishing it from sibling tools like 'get_adhoc_challenges' or '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 Guidelines2/5

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

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as 'get_adhoc_challenges' or 'get_available_badge_challenges', nor does it mention prerequisites or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nicolasvegam/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server