Skip to main content
Glama
johnnyinlee

lol-client-mcp Public

get_player_summoner_spells

Retrieve summoner spells for a League of Legends player by providing their Riot ID to access in-game data.

Instructions

Retrieve the list of the summoner spells for the player.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
riot_idYes

Implementation Reference

  • main.py:144-151 (handler)
    The handler function for the 'get_player_summoner_spells' tool. It makes an HTTP GET request to the League of Legends client API endpoint '/liveclientdata/playersummonerspells' with the provided riot_id parameter and returns the JSON response.
    @with_timeout
    async def get_player_summoner_spells(riot_id: str) -> dict:
        """
        Retrieve the list of the summoner spells for the player.
        """
        async with get_lol_client() as client:
            response = await client.get(f"/liveclientdata/playersummonerspells?riotId={riot_id}")
            return response.json()
  • main.py:143-143 (registration)
    Registers the 'get_player_summoner_spells' tool with the FastMCP server using the @mcp.tool() decorator.
    @mcp.tool()
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 tool retrieves data, implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns structured data, or handles errors. For a tool with zero annotation coverage, this is a significant gap in transparency.

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

Conciseness4/5

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

The description is a single, straightforward sentence with no wasted words. It's front-loaded with the core action ('Retrieve'), making it easy to parse. However, it could be slightly more specific (e.g., mentioning it's for a game context) to improve clarity without losing conciseness.

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 tool has no annotations, no output schema, and low schema description coverage, the description is incomplete. It doesn't cover behavioral aspects like authentication or error handling, parameter details, or return values. For a tool with such minimal structured data, the description should provide more context to be fully helpful.

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?

The schema description coverage is 0%, meaning the parameter 'riot_id' is undocumented in the schema. The description doesn't add any meaning beyond what the schema provides—it doesn't explain what a Riot ID is, its format, or how it's used. This fails to compensate for the low coverage, leaving the parameter poorly understood.

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 ('Retrieve the list of the summoner spells for the player') with a clear verb ('Retrieve') and resource ('summoner spells'), but it doesn't distinguish it from sibling tools like get_active_player_abilities or get_player_runes, which might retrieve similar player-related data. The purpose is understandable but lacks specificity about what makes this tool unique.

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 doesn't mention prerequisites (e.g., needing a valid Riot ID), exclusions, or how it differs from siblings like get_player_items or get_player_main_runes. This leaves the agent with minimal context for tool 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