Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_leagues

Retrieve League of Legends Esports leagues with IDs, slugs, names, regions, images, and display status so you can pass league IDs to schedule or tournament tools.

Instructions

League of Legends Esports leagues. Returns every league on lolesports.com with its numeric id, slug, name, region, image and display status (force_selected, selected, not_selected, hidden). Use a league id with lolesports-schedule or lolesports-tournaments. Region labels are upstream values such as EMEA, KOREA, CHINA, NORTH AMERICA and INTERNATIONAL.

Input Schema

NameRequiredDescriptionDefault
hlNoLanguage for names and labels; 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; defaults to en-US

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: 'Returns every league' discloses full-list/no-pagination behavior, and the display-status vocabulary (force_selected, selected, not_selected, hidden) plus the caveat that region labels are upstream values ('EMEA', 'KOREA') are genuinely useful context an agent could not infer. It never explicitly frames this as a read-only/no-auth call, which keeps it from a 5.

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?

Four sentences, front-loaded with the resource and return shape, then the chaining hint, then the region-label caveat. No filler, and each sentence supplies distinct information.

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?

No output schema exists, but the description compensates by enumerating the returned fields and their value domains for display status. For a one-optional-parameter read tool that is close to complete; only the localization link to `hl` and an explicit read-only framing are absent.

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% and the single `hl` parameter already documents its enum and default, so the baseline is 3. The description mentions 'name' and 'region' fields but never connects them to `hl` localization, adding nothing the schema does not already say.

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 league on lolesports.com' – and then enumerates the exact fields returned (numeric id, slug, name, region, image, display status). An agent can immediately distinguish this from lolesports_teams, lolesports_seasons, or lolesports_tournaments without inspecting schemas.

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 tells the agent how to chain the output: 'Use a league `id` with lolesports-schedule or lolesports-tournaments.' That is real routing guidance toward siblings. It does not state when NOT to use this tool (e.g. pick lolesports_seasons for season-level data), so it falls short of the 5 bar.

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

Deploy Server

Other Tools