Skip to main content
Glama
YuchengMaUTK

Unofficial WCA MCP Server

by YuchengMaUTK

search_competitions_by_event

Find World Cube Association competitions that feature a specific speedcubing event like 3x3x3 Cube or 3x3x3 Blindfolded. Use this tool to locate competitions by event ID with paginated results.

Instructions

Search for WCA competitions that include a specific event.

Returns competitions that feature the specified WCA event. Results are paginated to manage the response size.

Args: event_id: WCA event ID (e.g., "333" for 3x3x3 Cube, "222" for 2x2x2, "333bf" for 3x3x3 Blindfolded) page: Page number for pagination (default: 1)

Returns: Paginated competition data for competitions featuring the specified event

Example: search_competitions_by_event(event_id="333bf") - Competitions with 3x3x3 Blindfolded

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYes
pageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler decorated with @mcp.tool() that executes the search_competitions_by_event logic by delegating to WCAAPIClient.get_competitions_by_event
    @mcp.tool()
    async def search_competitions_by_event(
        event_id: str,
        page: int = 1
    ) -> Dict[str, Any]:
        """Search for WCA competitions that include a specific event.
        
        Returns competitions that feature the specified WCA event. Results are paginated
        to manage the response size.
        
        Args:
            event_id: WCA event ID (e.g., "333" for 3x3x3 Cube, "222" for 2x2x2, "333bf" for 3x3x3 Blindfolded)
            page: Page number for pagination (default: 1)
            
        Returns:
            Paginated competition data for competitions featuring the specified event
            
        Example:
            search_competitions_by_event(event_id="333bf") - Competitions with 3x3x3 Blindfolded
        """
        try:
            async with WCAAPIClient() as client:
                competitions_data = await client.get_competitions_by_event(event_id, page)
                return competitions_data
        except APIError as e:
            raise Exception(f"Failed to search competitions by event: {e}")
        except Exception as e:
            raise Exception(f"Unexpected error searching competitions by event: {e}")
  • Helper method in WCAAPIClient that constructs the WCA API endpoint for competitions by event and performs the HTTP request via _make_request
    async def get_competitions_by_event(
        self,
        event_id: str,
        page: int = 1
    ) -> Dict[str, Any]:
        """Get competitions that feature a specific event.
        
        Args:
            event_id: Event ID (e.g., "333", "222", "333bf")
            page: Page number (1-based)
            
        Returns:
            Paginated competition data for the event
        """
        if page == 1:
            endpoint = f"competitions/{event_id}.json"
        else:
            endpoint = f"competitions/{event_id}-page-{page}.json"
        return await self._make_request(endpoint)
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it specifies the tool returns paginated results to manage response size, describes what the output contains ('Paginated competition data'), and mentions the default value for the page parameter. It doesn't cover rate limits or authentication needs, but provides solid operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is efficiently structured with a clear purpose statement, behavioral details, parameter explanations, return information, and an example - all in well-organized sections. Every sentence adds value with zero waste.

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

Completeness5/5

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

Given the tool's moderate complexity (2 parameters, pagination), no annotations, and the presence of an output schema, the description is complete enough. It explains what the tool does, how to use it, parameter meanings, and behavioral characteristics without needing to detail return values since an output schema exists.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters: 'event_id' is described with examples of WCA event IDs, and 'page' is explained as the page number for pagination with its default value. This adds crucial meaning beyond the bare 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 clearly states the specific verb ('Search for') and resource ('WCA competitions') with precise scope ('that include a specific event'). It distinguishes from siblings like 'search_competitions_by_date' by specifying event-based filtering rather than date-based filtering.

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 (searching competitions by event) and includes an example. However, it doesn't explicitly mention when NOT to use it or name specific alternatives among the sibling tools, though the event-based focus is implied.

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