League of Legends MCP Server

LoL get clash player

lol_get_clash_player

Retrieve a player's Clash team and tournament information by providing their PUUID and platform region.

Instructions

Get Clash info for a player

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": {
      "puuid": "<puuid>"
    },
    "name": "lol_get_clash_player"
  }
}

Input Schema

Name	Required	Description	Default
`puuid`	Yes	Player PUUID
`platform`	No	Platform: euw1, eun1, na1, kr, jp1, br1, la1, la2, oc1, tr1, ru	euw1

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Jul 29, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations provided. Description fails to disclose behavioral traits such as authentication requirements, error conditions (e.g., player not in Clash), or whether the operation is read-only. A minimal description leaves agents without critical context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise at one sentence, but it lacks structure and additional informative content. No waste, but also no added value beyond the minimum.

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 no output schema, the description should hint at the response structure. 'Clash info' is too vague. Important context about what the tool returns is missing, making it incomplete for an agent to rely on.

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?

Input schema provides 100% coverage with descriptions for both parameters. The description adds no additional meaning beyond what the schema already states, so baseline score of 3 applies.

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?

Description clearly states the tool gets Clash info for a player, distinguishing it from sibling tools like lol_get_clash_tournaments and lol_get_clash_team. However, 'Clash info' is somewhat vague, missing specifics like whether it includes player stats or team details.

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 on when to use this tool vs alternatives. Does not mention prerequisites such as having the player's PUUID or that it should be used after obtaining a summoner. Lacks any usage context or exclusion cases.

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