Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_event

Retrieves League of Legends Esports match details by match ID, including league, tournament, teams, game wins, best-of strategy, game states, side assignments, VODs, and broadcast streams.

Instructions

League of Legends Esports match detail. Returns one match: league, tournament, teams with game wins, best-of strategy, each game's id, number, state (unneeded, unstarted, inProgress, completed), blue/red side assignment and VODs, plus broadcast streams. Use a game id with lolesports-game-window or lolesports-game-details. An unknown match id 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
match_idYesNumeric match id from lolesports-schedule, lolesports-live or lolesports-standings

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 full burden and does well: it states the cardinality (exactly one match), enumerates the returned structure, documents the game-state vocabulary (unneeded/unstarted/inProgress/completed), and discloses the not-found behavior for an unknown match id. It omits anything about caching, rate limits or latency, which keeps it short of 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 sentences, front-loaded with the purpose, then the payload description, then the sibling routing and error note. The field enumeration is dense but every item earns its place because there is no output schema to carry it.

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 and no annotations, so the description must supply both the return shape and the behavioral envelope — it supplies the full field list, the game-state enum, the one-match cardinality, downstream id usage, and the not-found case. 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% (baseline 3), and the description adds genuine value on top by clarifying that a game `id` from the response feeds different tools, implicitly distinguishing it from the match_id this tool requires — a common source of misuse. The "unknown match id returns not found" line gives the error semantics of the required parameter.

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?

The description opens with a specific verb+resource ("League of Legends Esports match detail. Returns one match") and then enumerates exactly what that match contains: league, tournament, teams with game wins, best-of strategy, per-game id/number/state, side assignment, VODs and streams. It distinguishes this single-match tool from the game-level siblings lolesports-game-window and lolesports-game-details.

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?

It gives an explicit routing rule for the downstream case: "Use a game `id` with lolesports-game-window or lolesports-game-details," which tells the agent when to leave this tool. It also warns about the failure mode of an unknown id. It doesn't explicitly say when to prefer this over lolesports_schedule or lolesports_live, but the parameter docs cover that source relationship.

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