Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_live

Retrieve League of Legends Esports matches currently in progress across all leagues. Returns an empty list when no league is playing.

Instructions

League of Legends Esports live matches. Returns matches currently in progress across all leagues, in the same shape as lolesports-schedule events. An empty list is valid when no league is playing. Pair a returned match id with lolesports-event to get game ids, then lolesports-game-window for live frames.

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/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses that results are live matches across all leagues, that an empty list is valid, and that the return shape matches lolesports-schedule events. However, it does not explicitly state read-only safety, auth requirements, rate limits, or pagination behavior, leaving some gaps for a no-annotation tool.

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?

The description is front-loaded with the core purpose, then adds only high-value details: return shape, empty-list behavior, and the recommended follow-up chain. Every sentence contributes useful information without repetition.

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?

For a simple live-match endpoint with one optional schema-documented parameter and no output schema, the description covers purpose, edge cases, return-shape reference, and downstream usage. It is nearly complete, though it could be slightly richer about the response object if the agent cannot rely solely on the lolesports-schedule comparison.

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?

The only parameter is hl, and the input schema has 100% description coverage including the full enum and default. The description adds no parameter-specific meaning, so the baseline score of 3 is appropriate because the schema already does the explanatory work.

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 states a specific verb and resource: 'Returns matches currently in progress across all leagues.' The phrase 'currently in progress' clearly separates this tool from schedule-oriented siblings, and the reference to 'the same shape as lolesports-schedule events' reinforces the distinction.

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 clear context for when to use this tool: to get live matches currently in progress, with the useful edge case that an empty list is valid when no league is playing. It also provides a downstream workflow via lolesports-event and lolesports-game-window, though it does not explicitly name lolesports-schedule as the alternative for non-live matches.

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