Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

lolesports_leagues

Read-only

Returns every League of Legends esports league on lolesports.com (LEC, LCK, LPL, LCS, Worlds, MSI and regional leagues) with numeric league id, slug, region and display status. Call this first to get a league id for lolesports_schedule or lolesports_tournaments. hl selects the language of names and defaults to en-US.

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": "lolesports_leagues"
  }
}

Input Schema

NameRequiredDescriptionDefault
hlNoOptional language code for names; defaults to en-US. One of cs-CZ, de-DE, en-US, es-ES, es-MX, fr-FR, hu-HU, ja-JP, ko-KR, pl-PL, pt-BR, th-TH, tr-TR, vi-VN, zh-TW.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds that the result is a complete enumeration of all leagues with no filtering, plus the id/slug/region/status shape. It does not discuss rate limits or whether inactive leagues are included.

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?

Three sentences, front-loaded with what is returned, then the routing instruction, then the parameter note. No filler; the parenthetical league examples earn their place by aiding tool selection.

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?

With an output schema present, return values need no elaboration, and the description covers purpose, sequencing, and the sole parameter. Minor gaps: nothing on whether the list includes historical/defunct leagues or how display status should be interpreted.

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% and the schema already lists every valid language code, so the description's note that hl selects the language of names and defaults to en-US is only a marginal addition (clarifying it affects names, not ids). Baseline 3 is appropriate.

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?

States a specific verb and resource (returns every LoL esports league on lolesports.com) and enumerates concrete members (LEC, LCK, LPL, LCS, Worlds, MSI). The distinction from siblings like lolesports_tournaments and lolesports_seasons is clear from the league-level scope.

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?

Explicitly instructs sequencing: "Call this first to get a league id for lolesports_schedule or lolesports_tournaments," which tells the agent when this tool is prerequisite rather than optional. It stops short of stating exclusions or when another lookup (e.g. lolesports_seasons) is preferable.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources