Skip to main content
Glama
johnnyinlee

lol-client-mcp Public

get_player_items

Retrieve a player's item list from League of Legends client data using their Riot ID.

Instructions

Retrieve the list of items for the player.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
riot_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:165-165 (registration)
    Registers the get_player_items tool using the FastMCP @mcp.tool() decorator.
    @mcp.tool()
  • main.py:167-173 (handler)
    The main handler function that fetches the player's items from the League of Legends client API endpoint `/liveclientdata/playeritems`, handles the HTTP request, and returns the JSON response.
    async def get_player_items(riot_id: str) -> list[dict]:
        """
        Retrieve the list of items for the player.
        """
        async with get_lol_client() as client:
            response = await client.get(f"/liveclientdata/playeritems?riotId={riot_id}")
            return response.json()
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 'retrieve' which implies a read operation, but doesn't cover permissions, rate limits, error handling, or what 'list of items' entails (e.g., format, pagination). For a tool with no 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.

Conciseness5/5

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

The description is a single, clear sentence with no wasted words. It's front-loaded with the core purpose, making it efficient and easy to parse. Every word earns its place, achieving optimal conciseness for such a simple statement.

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 1 parameter, no annotations, and an output schema exists (which handles return values), the description is minimally adequate. It states what the tool does but lacks details on behavior, usage context, or parameter specifics. For a simple retrieval tool, it meets the bare minimum but leaves gaps in guidance and transparency.

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 1 parameter with 0% description coverage, so the schema provides no semantic context. The description doesn't explicitly mention parameters, but it implies 'player' as the target, which aligns with the 'riot_id' parameter. Since there are 0 parameters documented in the schema, the baseline is 4, as the description adds some implicit meaning without contradiction.

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 'Retrieve the list of items for the player' clearly states the action (retrieve) and resource (items for player), but it's vague about what 'items' refers to (e.g., in-game items, inventory items) and doesn't differentiate from sibling tools like 'get_player_scores' or 'get_player_summoner_spells'. It avoids tautology by not just restating the name, but lacks specificity.

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 context (e.g., during a game, for inventory management) or exclusions, and with siblings like 'get_player_list' or 'get_all_game_data', there's no indication of how this tool fits into the broader API. This leaves the agent without usage direction.

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