Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_standings

Retrieve League of Legends Esports tournament standings, including stages, ordered team win-loss records, and linked playoff brackets, to track rankings and match progress.

Instructions

League of Legends Esports standings. Returns one tournament's stages (for example Regular Season, Playoffs), each with sections of matches and ordered team rankings with win-loss records. Playoff brackets include previous_match_ids that link rounds; rounds=true also names each bracket round. Use match ids with lolesports-event.

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
roundsNotrue adds each section's id and type (group or bracket) and bracket round names with their match ids; costs a second upstream call; false or omitted keeps the default response
tournament_idYesNumeric tournament id from lolesports-tournaments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.4/5.0
Behavior4/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 disclose the response's nested shape (stages → sections → rankings, bracket linkage via previous_match_ids). It stops short of stating that this is a read-only, non-mutating call and says nothing about caching, latency, or behavior for tournaments without standings.

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 tight sentences, front-loaded with the purpose before the return shape, then the bracket detail, then the sibling handoff. No restatement of the tool name or filler.

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, so the description has to describe the return structure, and it does so well for a nested response. Minor gaps remain around edge cases (tournament with no bracket, empty standings) and how stages map to tournament phases, but an agent can call it correctly as written.

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 already 100%, so the baseline is 3; the description goes beyond it by explaining that `rounds=true` adds bracket round names and that `previous_match_ids` link playoff rounds, which clarifies the payoff of the optional flag. It doesn't add anything about `hl` beyond the schema's own enumeration.

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 (LoL Esports standings) and precisely what it returns: one tournament's stages, sections of matches, and ordered team rankings with win-loss records. It also distinguishes itself from siblings by pointing to lolesports-tournaments as the tournament_id source and lolesports-event as the consumer of the returned match ids.

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?

The chaining instructions ('tournament_id from lolesports-tournaments', 'Use match ids with lolesports-event') give concrete when-to-use context and next-step routing. It lacks an explicit negative case (e.g., when to use standings vs schedule or completed events for the same tournament), so it stops short of full alternative guidance.

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