Skip to main content
Glama
johnnyinlee

lol-client-mcp Public

get_player_scores

Retrieve current player scores from League of Legends client data using Riot ID to track in-game performance metrics.

Instructions

Retrieve the list of the current scores for the player.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
riot_idYes

Implementation Reference

  • main.py:132-132 (registration)
    Registers the get_player_scores tool with the MCP server using the @mcp.tool() decorator.
    @mcp.tool()
  • main.py:132-141 (handler)
    The main handler function for the 'get_player_scores' tool. It makes an HTTP GET request to the League of Legends client API endpoint `/liveclientdata/playerscores` with the provided `riot_id` parameter and returns the JSON response containing the player's scores. Wrapped with timeout handling.
    @mcp.tool()
    @with_timeout
    async def get_player_scores(riot_id: str) -> dict:
        """
        Retrieve the list of the current scores for the player.
        """
        async with get_lol_client() as client:
            response = await client.get(f"/liveclientdata/playerscores?riotId={riot_id}")
            return response.json()
Behavior2/5

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

With no annotations, the description carries the full burden but lacks behavioral details. It doesn't specify if this is a read-only operation, requires authentication, has rate limits, or what the output format looks like (e.g., JSON structure, error handling). The description only states the basic action without additional context.

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 and efficiently conveys the core purpose, making it easy to parse quickly.

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 (a tool with one parameter but no annotations or output schema), the description is incomplete. It doesn't cover behavioral aspects, parameter meaning, or return values, making it inadequate for an agent to fully understand how to use this tool effectively.

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 but adds no parameter information. It doesn't explain what 'riot_id' is (e.g., a game identifier, player name), its format, or how it relates to retrieving scores, leaving the single required parameter undocumented beyond the schema.

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 resource ('list of the current scores for the player'), making the purpose understandable. It distinguishes from siblings like 'get_player_items' or 'get_player_summoner_spells' by focusing specifically on scores, though it doesn't explicitly contrast with them.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., during a game), or compare to siblings like 'get_game_stats' or 'get_all_game_data', 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