League of Legends MCP Server

LoL get live game

lol_get_live_game

Determine if a player is currently in an active League of Legends game by providing their summoner ID and region.

Instructions

Check if a player is currently in game

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "summonerId": "<summonerId>"
    },
    "name": "lol_get_live_game"
  }
}

Input Schema

Name	Required	Description	Default
`platform`	No	Platform: euw1, eun1, na1, kr, jp1, br1, la1, la2, oc1, tr1, ru	euw1
`summonerId`	Yes	Summoner ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Jul 29, 2026

TDQS

B3.4/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 full burden for behavioral transparency. It only states the purpose, lacking any disclosure about authentication needs, rate limits, or what happens when the player is not in a game.

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 efficient sentence with no wasted words. It is front-loaded and immediately clear.

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 too minimal. It does not explain what data is returned (e.g., game details) or handle edge cases, making it incomplete for a tool that likely has more context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description adds no additional meaning beyond the schema. The baseline score of 3 is appropriate as the description does not enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Check if a player is currently in game'. It uses specific verb 'check' and resource 'player', and it distinguishes itself from sibling tools like match history or summoner info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for checking live game status, but it does not explicitly state when to use this tool vs alternatives, nor does it provide any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.