lol-client-mcp Public
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_game_dataA | The Live League of Legends Client Data API has a number of endpoints that return a subset of the data returned by the /allgamedata endpoint. This endpoint is great for testing the Live Client Data API, but unless you actually need all the data from this endpoint, use one of the endpoints listed below that return a subset of the response. |
| get_active_playerC | Get all data about the active player. |
| get_active_player_nameC | Returns the player name. |
| get_active_player_abilitiesC | Get Abilities for the active player. |
| get_active_player_runesB | Retrieve the full list of runes for the active player. |
| get_player_listB | Retrieve the list of heroes in the game and their stats. |
| get_player_scoresC | Retrieve the list of the current scores for the player. |
| get_player_summoner_spellsC | Retrieve the list of the summoner spells for the player. |
| get_player_main_runesC | Retrieve the basic runes of any player. |
| get_player_itemsB | Retrieve the list of items for the player. |
| get_event_dataC | Get a list of events that have occurred in the game. |
| get_game_statsD | Basic data about the game. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Multiple tools have overlapping or unclear boundaries, causing potential confusion. For example, get_active_player_abilities, get_active_player_runes, and get_player_main_runes could be confused with each other or with get_active_player, and get_all_game_data overlaps in scope with several other tools like get_game_stats and get_event_data. The descriptions do not clearly differentiate these tools, leading to ambiguity in selection.
The naming is mostly consistent with a verb_noun pattern (e.g., get_active_player, get_game_stats), but there are minor deviations such as get_all_game_data using 'all' as a prefix and get_player_main_runes using 'main' as an adjective. Overall, the naming is readable and follows a predictable structure, with only slight inconsistencies.
With 12 tools, the count is reasonable for a League of Legends client data server, covering various aspects like player data, game stats, and events. It is slightly on the higher side but still well-scoped, as each tool targets specific data subsets, though some overlap exists. The number is appropriate for the domain without being excessive.
The tool set covers key data retrieval aspects such as player info, game stats, and events, but there are notable gaps. For instance, it lacks update or action-oriented tools (e.g., for interacting with the game), and some tools like get_all_game_data may duplicate others, reducing efficiency. While agents can work with the provided tools, the surface is not fully comprehensive for a complete client interaction experience.