Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_schedule

Fetch League of Legends Esports match schedules around today with start times, states, leagues, teams, outcomes, and best-of details; filter by league and page through past or future matches.

Instructions

League of Legends Esports schedule. Returns the match schedule around today: start time, state (unstarted, inProgress, completed), block name, league, teams, outcome and game wins, and best-of strategy. Optionally filter with league_id. Follow older_page_token for past results and newer_page_token for later fixtures; a missing token means that direction is exhausted.

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
league_idNoNumeric league id from lolesports-leagues, or up to 10 comma-separated ids to combine leagues; omit for all leagues
page_tokenNoolder_page_token or newer_page_token copied from a previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses that results are centered on today, what fields come back (state enum values, teams, outcome, game wins, best-of), and the pagination contract (missing `older_page_token`/`newer_page_token` means that direction is exhausted). It omits auth/rate-limit context, so not 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?

Two tight sentences, front-loaded with purpose then payload then filtering then pagination; every clause conveys something an agent needs and nothing is redundant.

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 enumerates the returned fields and the state values, and it explains pagination — everything needed to call a three-parameter, read-only schedule tool correctly.

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 the baseline is 3, but the description adds meaning beyond the schema by explaining the directional semantics of the page tokens and the exhaustion rule, which the schema only hints at. `hl` is left to the schema, keeping it out of a 5.

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 ('League of Legends Esports schedule ... returns the match schedule around today') and enumerates the returned fields, so an agent can immediately tell it apart from siblings like lolesports_completed_events, lolesports_live, or lolesports_event.

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?

Explains that results center on today and that `league_id` optionally narrows by league, which implicitly frames when to reach for it versus event/game-detail tools. It does not explicitly name alternatives or exclusions, so it stops short of a 5.

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