Skip to main content
Glama
johnnyinlee

lol-client-mcp Public

get_event_data

Retrieve real-time game event data from the League of Legends client to monitor in-game occurrences and track match progress.

Instructions

Get a list of events that have occurred in the game.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:178-184 (handler)
    The main handler function for the 'get_event_data' tool. It fetches event data from the League of Legends live client API endpoint '/liveclientdata/eventdata' using an HTTP client with timeout handling.
    async def get_event_data() -> dict:
        """
        Get a list of events that have occurred in the game.
        """
        async with get_lol_client() as client:
            response = await client.get("/liveclientdata/eventdata")
            return response.json()
  • main.py:176-176 (registration)
    The @mcp.tool() decorator registers the get_event_data function as an MCP tool in the FastMCP server.
    @mcp.tool()
  • Applies the with_timeout decorator to handle various HTTP errors and timeouts for the tool.
    @with_timeout
  • main.py:50-58 (helper)
    Helper function to create the HTTP client configured for the LoL client API, used by get_event_data.
    def get_lol_client():
        """
        Create an HTTP client for the League of Legends client.
        """
        return httpx.AsyncClient(
            base_url=LOL_CLIENT_HOST,
            verify="./certs/riotgames.pem",
            timeout=DEFAULT_TIMEOUT
        )
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 states the tool 'gets' events, implying a read-only operation, but does not disclose behavioral traits such as whether it returns real-time or historical data, any rate limits, error conditions, or the format of the returned list. This is a significant gap for a tool with no annotation coverage.

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 a single, clear sentence with no wasted words. It is front-loaded and efficiently conveys the core purpose without unnecessary elaboration, making it easy for an agent to parse quickly.

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 complexity (a tool to retrieve game events), lack of annotations, and no output schema, the description is incomplete. It does not explain what the returned events include, their structure, or any limitations, which is inadequate for proper tool invocation by an agent.

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 there are no parameters to document. The description does not need to add parameter semantics, and it appropriately does not mention any. Baseline is 4 for zero parameters, as the schema fully covers the lack of inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose ('Get a list of events') and specifies the resource ('events that have occurred in the game'), which is clear. However, it lacks specificity about what types of events or how they are filtered, and it does not differentiate from siblings like 'get_game_stats' or 'get_all_game_data' that might overlap in scope.

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 does not mention any context, prerequisites, or exclusions, leaving the agent to infer usage based on the name alone among many sibling tools related to game data.

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/johnnyinlee/lol-client-mcp'

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