Crawlora MCP

lolesports_live

Read-only

Returns League of Legends esports matches in progress right now across all leagues, in the same event shape as lolesports_schedule. 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lolesports_live"
  }
}

Input Schema

Name	Required	Description	Default
`hl`	No	Optional language code; defaults to en-US.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses two non-obvious traits: no per-league filtering (all leagues) and that an empty result is a legitimate outcome rather than an error. It does not discuss rate limits or refresh cadence for a live feed, which keeps it below 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?

Three short sentences: what it returns, the output-shape parity and empty-case caveat, then the follow-up chain. Scope is front-loaded and every sentence carries information.

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?

An output schema exists so return values need no explanation, yet the description still anchors the response shape to lolesports_schedule and warns about the empty case. Combined with the documented follow-up tools, nothing needed to call or act on this tool is missing.

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 single optional 'hl' parameter is fully documented in the schema (100% coverage, defaults to en-US) and is never mentioned in the description. With schema coverage this high, the baseline of 3 applies – the description adds nothing but loses nothing.

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+resource+scope: 'Returns League of Legends esports matches in progress right now across all leagues.' This distinguishes it from lolesports_schedule (which it references only for output shape) and from lolesports_completed_events, so an agent can select it without opening the schema.

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 phrase 'in progress right now' plus 'An empty list is valid when no league is playing' clarifies the temporal condition and edge case, and the follow-up chain (event id -> lolesports_event -> lolesports_game_window) tells the agent what to do next. It stops short of explicitly naming the alternative for future/past matches, so it is not a full when/when-not statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?