League of Legends MCP Server

LoL get challenges

lol_get_challenges

Fetch all challenge configurations for a specified platform, including challenge IDs, thresholds, and rewards.

Instructions

Get all challenge configurations

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lol_get_challenges"
  }
}

Input Schema

Name	Required	Description	Default
`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

B3.3/5.0

Behavior2/5

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

No annotations provided, so description must carry full burden. It discloses no behavioral traits such as read-only nature, rate limits, or authentication needs. Minimal transparency beyond the action itself.

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?

Single sentence with zero wasted words. Efficiently front-loads the purpose.

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

Completeness3/5

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

Adequate for a simple tool with one optional parameter and no output schema, but lacks explanation of what 'challenge configurations' entails or the return format. Minimal completeness.

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% for the single optional parameter 'platform', including defaults and allowed values. The description adds no additional meaning, meeting but not exceeding the baseline of 3.

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?

Description 'Get all challenge configurations' provides a clear verb and resource. It distinguishes this global config retrieval from sibling tools like 'lol_get_player_challenges' which fetch player-specific data.

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 (e.g., when to use lol_get_player_challenges instead). No context about prerequisites or use cases.

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