Skip to main content
Glama
johnnyinlee

lol-client-mcp Public

get_game_stats

Retrieve basic game data from the League of Legends client to access current match statistics and player information.

Instructions

Basic data about the game.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:187-195 (handler)
    The handler function for the 'get_game_stats' tool. It is decorated with @mcp.tool() for registration and @with_timeout for error handling. It fetches basic game stats data from the League of Legends live client API endpoint '/liveclientdata/gamestats' using an HTTP client.
    @mcp.tool()
    @with_timeout
    async def get_game_stats() -> dict:
        """
        Basic data about the game.
        """
        async with get_lol_client() as client:
            response = await client.get("/liveclientdata/gamestats")
            return response.json()
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Basic data about the game' reveals nothing about whether this is a read operation, what permissions might be needed, whether it's cached or real-time, rate limits, or what format the response takes. For a tool with zero annotation coverage, this description provides no behavioral context.

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

Conciseness2/5

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

While technically concise with just 4 words, this is under-specification rather than effective conciseness. The single sentence 'Basic data about the game' doesn't earn its place by providing meaningful information. A truly concise description would still convey essential purpose and differentiation from siblings.

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

Completeness1/5

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

Given the complexity of game data retrieval tools (11 siblings), no annotations, and no output schema, the description is completely inadequate. It doesn't explain what 'basic data' means, how it differs from 'all game data' or 'event data', what the return format is, or any behavioral characteristics. For a tool in this rich context, the description fails to provide necessary completeness.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the parameter situation. The description doesn't need to compensate for any parameter gaps. The baseline for 0 parameters with complete schema coverage is 4, as there are no parameters whose semantics need explanation beyond what the schema provides.

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

Purpose2/5

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

The description 'Basic data about the game' is vague and tautological - it essentially restates the tool name 'get_game_stats' without specifying what kind of data or what aspect of the game. It doesn't distinguish this tool from siblings like 'get_all_game_data' or 'get_event_data' which also retrieve game-related information. The description lacks a specific verb and resource scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance on when to use this tool versus alternatives. With 11 sibling tools that all retrieve game-related data, there's no indication whether this tool provides summary statistics, real-time game state, or metadata. No context about appropriate use cases or exclusions is mentioned.

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