Skip to main content
Glama
johnnyinlee

lol-client-mcp Public

by johnnyinlee
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_active_player_abilities

Retrieve ability information for the currently active player in League of Legends to access cooldowns, levels, and descriptions during gameplay.

Instructions

Get Abilities for the active player.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:99-108 (handler)
    The handler function decorated with @mcp.tool() and @with_timeout that fetches the active player's abilities from the League of Legends live client API endpoint and returns the JSON response.
    @mcp.tool()
@with_timeout
async def get_active_player_abilities() -> dict:
    """
    Get Abilities for the active player.
    """
    async with get_lol_client() as client:
        response = await client.get("/liveclientdata/activeplayerabilities")
        return response.json()

Tool Definition Quality

C2.9/5.0
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. The description only states what the tool does ('Get Abilities') without revealing any behavioral traits such as whether it's read-only, requires authentication, has rate limits, or what format the output might be in. For a tool with zero annotation coverage, this leaves critical gaps in understanding its operation and constraints.

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—just one sentence—and front-loaded with the core action ('Get Abilities'). There is no wasted verbiage or redundancy, making it efficient and easy to parse. Every word earns its place by directly stating the tool's purpose without unnecessary elaboration.

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 lack of annotations and output schema, the description is incomplete for effective tool use. It does not explain what 'Abilities' entail (e.g., skill names, cooldowns, levels), how the data is returned, or any behavioral context. While the tool has no parameters, the description fails to compensate for the missing output and behavioral information, leaving the agent with insufficient context.

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 tool has 0 parameters, and the schema description coverage is 100%, meaning there are no parameters to document. The description does not need to add parameter semantics beyond the schema, as there are none. A baseline score of 4 is appropriate since the absence of parameters is correctly reflected, and no additional explanation is required.

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 as 'Get Abilities for the active player,' which is a clear verb+resource combination. However, it does not differentiate this tool from its siblings (e.g., get_active_player_runes, get_player_summoner_spells), leaving ambiguity about what specifically distinguishes 'abilities' from other player attributes. The purpose is understandable but lacks specificity in the context of available alternatives.

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 its siblings. It does not mention alternatives, prerequisites, or contextual cues (e.g., when abilities are needed vs. runes or items). Without any usage instructions, the agent must infer based on tool names alone, which is insufficient for optimal 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