Skip to main content
Glama
YuchengMaUTK

Unofficial WCA MCP Server

by YuchengMaUTK

get_wca_events

Retrieve official World Cube Association speedcubing events with their IDs, names, and formats for competition data access.

Instructions

Get all official WCA events.

Returns a list of all official World Cube Association events including event IDs, names, and formats.

Returns: List of WCA events with their details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function implementing the get_wca_events tool. Decorated with @mcp.tool() for automatic registration in FastMCP. Fetches official WCA events via WCAAPIClient.get_events() and handles errors.
    @mcp.tool()
    async def get_wca_events() -> List[Dict[str, Any]]:
        """Get all official WCA events.
        
        Returns a list of all official World Cube Association events including
        event IDs, names, and formats.
        
        Returns:
            List of WCA events with their details
        """
        try:
            async with WCAAPIClient() as client:
                events = await client.get_events()
                return events
        except APIError as e:
            raise Exception(f"Failed to fetch WCA events: {e}")
        except Exception as e:
            raise Exception(f"Unexpected error fetching WCA events: {e}")
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the return type but doesn't disclose behavioral traits like rate limits, authentication needs, or whether the data is static or frequently updated. The description is minimal beyond stating the output.

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 front-loaded with the core purpose in the first sentence, followed by specifics on returns. Every sentence adds value without redundancy, making it efficiently structured.

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's simplicity (0 parameters, output schema provided), the description is reasonably complete. It explains what the tool does and the return content, though it could benefit from more behavioral context given the lack of annotations.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a high baseline score for not adding unnecessary information.

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 verb 'Get' and the resource 'all official WCA events', specifying it returns event IDs, names, and formats. It distinguishes from siblings like get_competition_event_results or get_rankings by focusing on event metadata rather than competition-specific data.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the purpose alone.

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