League of Legends MCP Server

LoL get account

lol_get_account

Retrieve Riot account information using a player's game name and tag line. Specify region to get account details.

Instructions

Get Riot account info by Riot ID (gameName#tagLine)

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": {
      "gameName": "<gameName>",
      "tagLine": "<tagLine>"
    },
    "name": "lol_get_account"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No	Region: euw, eune, na, kr, br, lan, las, oce, ru, tr, jp, ph2, sg2, th2, tw2, vn2	euw
`tagLine`	Yes	Tag line (e.g. EUW, KR1)
`gameName`	Yes	Game name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Jul 29, 2026

TDQS

A4/5.0

Behavior3/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. It implies a read operation but does not disclose potential side effects, authentication requirements, error handling (e.g., account not found), or rate limits. For a simple retrieval, the gap is moderate.

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, front-loaded sentence that conveys the essential information with no extraneous words. Every part is necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity and full schema coverage, the description adequately explains the tool's purpose and input. It explicitly mentions the Riot ID format. However, it does not describe the return value (e.g., account details like puuid, summoner level), which would add completeness but is not critical since the tool name implies the output.

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 description coverage is 100%, with each parameter having a description. The tool description does not add additional semantics beyond the schema (e.g., explaining the format of tagLine or region). According to guidelines, baseline 3 is appropriate when coverage is high.

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 uses a specific verb ('Get') and resource ('Riot account info'), and clarifies the input format ('Riot ID (gameName#tagLine)'). It clearly distinguishes from sibling tools that focus on game data, matches, champions, etc.

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

Usage Guidelines4/5

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

The description states the input format, making it clear when to use the tool (when you have a Riot ID). However, it does not explicitly mention when not to use it or provide alternatives among siblings. Since no other sibling tool retrieves account info, the context is sufficient but lacks exclusions.

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