Skip to main content
Glama
enesjakozh
johnnyinlee

lol-client-mcp Public

by johnnyinlee
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_active_player_runes

Retrieve the active player's current rune setup from the League of Legends client to analyze gameplay configuration.

Instructions

Retrieve the full list of runes for the active player.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:110-118 (handler)
    The handler function implementing the 'get_active_player_runes' MCP tool. It uses the @mcp.tool() decorator for registration and @with_timeout decorator for error handling. Fetches the active player's runes from the League of Legends live client API endpoint.
    @mcp.tool()
@with_timeout
async def get_active_player_runes() -> dict:
    """
    Retrieve the full list of runes for the active player.
    """
    async with get_lol_client() as client:
        response = await client.get("/liveclientdata/activeplayerrunes")
        return response.json()

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is to 'Retrieve', implying a read-only operation, but does not clarify aspects like data freshness, error conditions, or response format. This leaves gaps in understanding how the tool behaves beyond its basic function.

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 that directly states the tool's function without unnecessary words. It is front-loaded and efficiently conveys the essential information, making it easy to parse and understand quickly.

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 the tool has no parameters and no output schema, the description adequately covers the basic purpose. However, it lacks details on the return value (e.g., format of the rune list) and behavioral context, which could be important for an agent to use it effectively, especially with no annotations to supplement.

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 does not add parameter details, which is appropriate here, but it could have mentioned if any implicit parameters (like context or state) are involved, though not required for a baseline score.

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 action ('Retrieve') and the resource ('full list of runes for the active player'), making the purpose understandable. However, it does not explicitly differentiate this tool from sibling tools like 'get_player_main_runes' or 'get_player_items', which might also involve rune-related data, leaving some ambiguity about its unique 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, such as 'get_player_main_runes' or 'get_all_game_data'. It lacks context about prerequisites, timing, or specific use cases, leaving the agent to infer usage based on the name 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/johnnyinlee/lol-client-mcp'

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