Skip to main content
Glama
johnnyinlee

lol-client-mcp Public

get_player_main_runes

Retrieve basic rune setups for League of Legends players by entering their Riot ID. This tool accesses live client data to display current rune configurations.

Instructions

Retrieve the basic runes of any player.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
riot_idYes

Implementation Reference

  • main.py:154-162 (handler)
    The main handler function for the 'get_player_main_runes' tool. It is decorated with @mcp.tool() for registration and @with_timeout. It fetches the player's main runes from the League of Legends live client API using the provided riot_id.
    @mcp.tool()
    @with_timeout
    async def get_player_main_runes(riot_id: str) -> dict:
        """
        Retrieve the basic runes of any player.
        """
        async with get_lol_client() as client:
            response = await client.get(f"/liveclientdata/playermainrunes?riotId={riot_id}")
            return response.json()
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 only states the action ('Retrieve') without mentioning whether this is a read-only operation, requires authentication, has rate limits, or what the output looks like. This is inadequate for a tool with zero 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 extremely concise with a single sentence that directly states the tool's purpose. It's front-loaded and wastes no words, making it efficient for quick understanding.

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 (1 parameter with 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain parameters, behavioral traits, or output, leaving significant gaps for an AI agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate by explaining parameters. It doesn't mention the 'riot_id' parameter at all, leaving it undocumented. The description adds no meaning beyond the schema, failing to address the coverage gap.

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 purpose ('Retrieve the basic runes of any player') with a clear verb ('Retrieve') and resource ('basic runes'), but it's vague about what 'basic runes' means compared to sibling tools like 'get_active_player_runes'. It doesn't distinguish itself from siblings, making it unclear if this is for active games or general player 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 like 'get_active_player_runes' or 'get_player_list'. It mentions 'any player' but doesn't specify context (e.g., in-game vs. profile data) or prerequisites, leaving usage ambiguous.

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