Skip to main content
Glama
johnnyinlee

lol-client-mcp Public

get_player_list

Retrieve a list of game heroes and their stats from the League of Legends client to access current player data.

Instructions

Retrieve the list of heroes in the game and their stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:123-130 (handler)
    The core handler function for the 'get_player_list' tool. It makes an HTTP GET request to the League of Legends live client API at '/liveclientdata/playerlist' and returns the JSON response as a list of dictionaries containing player stats.
    async def get_player_list() -> list[dict]:
        """
        Retrieve the list of heroes in the game and their stats.
        """
        async with get_lol_client() as client:
            response = await client.get("/liveclientdata/playerlist")
            return response.json()
  • main.py:121-121 (registration)
    Registers the get_player_list function as an MCP tool using the FastMCP decorator. The tool name is inferred from the function name.
    @mcp.tool()
  • Applies the with_timeout decorator to handle timeouts and errors in the HTTP requests made by the tool.
    @with_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 of behavioral disclosure. It states the action ('Retrieve') but doesn't mention any traits like read-only status, potential rate limits, authentication needs, or what happens if no data is available. This leaves significant gaps for a tool that likely interacts with game data.

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, efficient sentence that directly states the tool's function without any wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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

Completeness3/5

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

Given that there's an output schema (which should cover return values), no parameters, and no annotations, the description is minimally adequate. However, for a tool that retrieves game data, it lacks context on data scope (e.g., all heroes vs. filtered) and behavioral traits, leaving room for improvement despite the structured support.

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, meaning no parameters are documented in the schema. The description doesn't add parameter details, but since there are no parameters, this is acceptable. A baseline of 4 is appropriate as it doesn't need to compensate for missing schema information.

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

Purpose4/5

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

The description clearly states the verb ('Retrieve') and resource ('list of heroes in the game and their stats'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'get_player_items' or 'get_player_scores', which also retrieve player-related data, so it misses the highest score.

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. With siblings like 'get_active_player' (which might retrieve a single player) and 'get_all_game_data' (which might include broader data), there's no indication of context, exclusions, or prerequisites for selection.

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