Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_seasons

Retrieve the League of Legends esports calendar since 2011, including each season’s splits, regions, tournaments, league IDs, and season IDs for standings and tournament lookups.

Instructions

League of Legends Esports seasons and splits. Returns the League of Legends esports calendar since 2011, newest first: every season with its splits (start and end time, region) and the tournaments played in each split with their league. Use a tournament id with lolesports-standings or lolesports-completed-events and a league id with lolesports-tournaments. season_id (taken from an earlier response) returns one season; region keeps only splits of one region and league_id keeps only that league's tournaments, both applied after the fetch. The unfiltered list is large (about 300 KB). A season id that does not exist returns not found.

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
regionNoSplit region, case-insensitive; one of AMERICAS, BRAZIL, CHINA, COMMONWEALTH OF INDEPENDENT STATES, EMEA, EUROPE, GLOBAL, HONG KONG, MACAU, TAIWAN, INTERNATIONAL, JAPAN, KOREA, LATIN AMERICA, LATIN AMERICA NORTH, LATIN AMERICA SOUTH, NORTH AMERICA, OCEANIA, REGIONAL, SOUTHEAST ASIA, TURKEY, VIETNAM
league_idNoNumeric league id from lolesports-leagues; keeps only that league's tournaments
season_idNoNumeric season id from an earlier lolesports-seasons response; omit for every season

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does it well: newest-first ordering, 2011 cutoff, ~300 KB unfiltered payload size, that `region`/`league_id` are applied AFTER the fetch (a real performance caveat), and that a bad season id returns not found. These are non-obvious operational facts absent from any structured field.

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

Conciseness4/5

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

Front-loaded with the resource and return shape, then the non-obvious caveats (id chaining, payload size, post-fetch filtering). Dense but every sentence earns its place; slightly overpacked with three distinct concerns in one paragraph.

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

Completeness5/5

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

No output schema exists, yet the description explains the returned hierarchy (season → splits → tournaments) and the size/ordering behavior. With four optional params and no annotations, nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds meaning beyond the schema: it clarifies `season_id` comes from an earlier response, and that `region` filters splits while `league_id` filters tournaments, plus that both are post-fetch filters. Only `hl` is left entirely to the schema, which is acceptable given its enum is fully documented.

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 resource (League of Legends esports seasons and splits) and a specific verb behavior, then spells out the return shape: seasons with splits (start/end time, region) and tournaments with their league, newest first since 2011. An agent can distinguish this from lolesports-leagues or lolesports-tournaments purely from the description.

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

Usage Guidelines5/5

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

Explicitly routes downstream: tournament `id` goes to lolesports-standings/completed-events, league `id` to lolesports-tournaments. Also states when to use `season_id` (single season) versus omitting it (all seasons), which is exactly the when-to-use guidance an agent needs.

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