Skip to main content
Glama
YuchengMaUTK

Unofficial WCA MCP Server

by YuchengMaUTK

get_competition_results

Retrieve comprehensive speedcubing competition results including solve times, rankings, and round-by-round data from World Cube Association events.

Instructions

Get all results for a WCA competition.

Returns comprehensive results data for all events in a competition, including competitor performances, solve breakdowns, round information, and final rankings. This provides complete competition outcome data.

Args: competition_id: WCA competition ID (e.g., "WC2023", "CubingUSANationals2024")

Returns: Complete results data for all events in the competition including: - Individual solve times and averages - Round-by-round progression - Final rankings and positions - DNF/DNS information - Competitor details

Example: get_competition_results("WC2023") - All results from World Championship 2023

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
competition_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function for 'get_competition_results' decorated with @mcp.tool(). It creates a WCAAPIClient instance and calls its get_competition_results method to fetch and return the competition results data.
    @mcp.tool()
    async def get_competition_results(competition_id: str) -> Dict[str, Any]:
        """Get all results for a WCA competition.
        
        Returns comprehensive results data for all events in a competition,
        including competitor performances, solve breakdowns, round information,
        and final rankings. This provides complete competition outcome data.
        
        Args:
            competition_id: WCA competition ID (e.g., "WC2023", "CubingUSANationals2024")
            
        Returns:
            Complete results data for all events in the competition including:
            - Individual solve times and averages
            - Round-by-round progression
            - Final rankings and positions
            - DNF/DNS information
            - Competitor details
            
        Example:
            get_competition_results("WC2023") - All results from World Championship 2023
        """
        try:
            async with WCAAPIClient() as client:
                results_data = await client.get_competition_results(competition_id)
                return results_data
        except APIError as e:
            raise Exception(f"Failed to get results for competition {competition_id}: {e}")
        except Exception as e:
            raise Exception(f"Unexpected error getting results for competition {competition_id}: {e}")
  • Core helper method in the WCAAPIClient class that performs the HTTP GET request to the WCA static API endpoint for competition results (results/{competition_id}.json).
    async def get_competition_results(
        self,
        competition_id: str
    ) -> Dict[str, Any]:
        """Get all results for a competition.
        
        Args:
            competition_id: Competition ID
            
        Returns:
            All result data for the competition
        """
        return await self._make_request(f"results/{competition_id}.json")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it describes what data is returned, it doesn't mention important behavioral aspects like rate limits, authentication requirements, error conditions, pagination, or data freshness. For a data retrieval tool with no annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 well-structured with clear sections (purpose, returns, args, example) and front-loaded information. Every sentence adds value, though the 'Returns' section could be slightly more concise. The structure helps the agent quickly understand the tool's purpose and usage.

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?

Given the tool has an output schema (which handles return value documentation) and only one parameter that's well-explained in the description, the description is reasonably complete. It covers the core purpose, parameter meaning, and provides an example. The main gap is lack of behavioral context (rate limits, errors, etc.) which would be more critical for complex tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides excellent parameter semantics despite 0% schema description coverage. It clearly explains the 'competition_id' parameter with a definition ('WCA competition ID'), format examples ('WC2023', 'CubingUSANationals2024'), and usage in the example. This fully compensates for the lack of schema descriptions and adds meaningful context beyond what the bare schema provides.

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 clearly states the tool's purpose: 'Get all results for a WCA competition' with specific details about what data is returned (competitor performances, solve breakdowns, round information, final rankings). It distinguishes from siblings like 'get_competition_event_results' by specifying 'all events' rather than a single event, but doesn't explicitly contrast with other similar tools like 'get_competition_by_id'.

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 description implies usage context through the example and parameter explanation, showing this is for retrieving complete competition results. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_competition_by_id' (which might return metadata) or 'get_competition_event_results' (which focuses on single events). The guidance is present but not comprehensive.

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/YuchengMaUTK/unofficial-wca-mcp-server'

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