Skip to main content
Glama
YuchengMaUTK

Unofficial WCA MCP Server

by YuchengMaUTK

get_championship_details

Retrieve comprehensive details for any WCA championship including venue information, events, results, competitors, and regional significance using the championship ID.

Instructions

Get detailed information about a specific championship by its ID.

Returns comprehensive information about a WCA championship including venue details, events, results, competitors, and championship-specific information like regional significance.

Args: championship_id: Championship ID (e.g., "WC2023" for World Championship 2023, "Euro2022" for European Championship 2022)

Returns: Detailed championship information including all competition data plus championship-specific details

Example: get_championship_details("WC2023") - World Championship 2023 details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
championship_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the 'get_championship_details' MCP tool. It is decorated with @mcp.tool() for automatic registration and implements the core logic by calling WCAAPIClient.get_championship() to fetch and return the data.
    @mcp.tool()
    async def get_championship_details(championship_id: str) -> Dict[str, Any]:
        """Get detailed information about a specific championship by its ID.
        
        Returns comprehensive information about a WCA championship including
        venue details, events, results, competitors, and championship-specific
        information like regional significance.
        
        Args:
            championship_id: Championship ID (e.g., "WC2023" for World Championship 2023,
                            "Euro2022" for European Championship 2022)
            
        Returns:
            Detailed championship information including all competition data
            plus championship-specific details
            
        Example:
            get_championship_details("WC2023") - World Championship 2023 details
        """
        try:
            async with WCAAPIClient() as client:
                championship_data = await client.get_championship(championship_id)
                return championship_data
        except APIError as e:
            raise Exception(f"Failed to get championship {championship_id}: {e}")
        except Exception as e:
            raise Exception(f"Unexpected error getting championship {championship_id}: {e}")
  • Supporting helper method in WCAAPIClient that performs the actual API request to retrieve championship details from the WCA static API endpoint.
    async def get_championship(self, championship_id: str) -> Dict[str, Any]:
        """Get a specific championship by ID.
        
        Args:
            championship_id: Championship ID
            
        Returns:
            Championship data
        """
        return await self._make_request(f"championships/{championship_id}.json")
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that it 'Returns comprehensive information' and lists what's included (venue, events, results, competitors, regional significance), which is good behavioral context. However, it doesn't mention potential limitations like rate limits, authentication needs, error conditions, or whether it's a read-only operation (though 'Get' implies safe read).

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 appropriately sized and well-structured: purpose statement first, then returns information, followed by args and returns sections with clear formatting. The example at the end is helpful. Some minor redundancy exists (e.g., 'detailed information' and 'comprehensive information'), but overall it's efficient with every sentence adding value.

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 1 parameter with 0% schema coverage but an output schema exists, the description provides good context: it explains the parameter meaning with examples and outlines what information will be returned. The existence of an output schema means it doesn't need to detail return values. For a simple lookup tool with one parameter, this is reasonably complete, though it could mention if there are any prerequisites or limitations.

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?

The schema description coverage is 0%, so the description must compensate. It provides the parameter name 'championship_id' with clear semantics: 'Championship ID' with helpful examples ('WC2023' for World Championship 2023, 'Euro2022' for European Championship 2022). This adds meaningful context beyond the bare schema, though it doesn't specify format constraints beyond the examples.

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 clearly states the specific action ('Get detailed information') and resource ('about a specific championship by its ID'), distinguishing it from siblings like 'get_competition_by_id' by specifying it returns 'championship-specific information like regional significance' and comprehensive competition data. It explicitly mentions it's for WCA championships with examples like 'WC2023' and 'Euro2022'.

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?

The description provides clear context for when to use this tool: when you need 'detailed information about a specific championship by its ID' and want 'comprehensive information' including 'championship-specific details'. It implies usage vs. siblings by specifying championship focus, but doesn't explicitly state when not to use it or name alternatives like 'get_competition_by_id' for non-championship competitions.

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