Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_game_window

Fetch a League of Legends Esports game’s live-stats window, including patch, team/player metadata, and ~10 seconds of frames with gold, kills, objectives, and player stats.

Instructions

League of Legends Esports live game window. Returns the lolesports live-stats window for one game: patch, blue and red team and player metadata (champion, role, summoner name) and roughly ten seconds of frames with team gold, kills, towers, inhibitors, barons, dragons and per-player level, KDA, creep score and health. game_state is in_game, paused or finished. For a game in progress omit starting_time for the latest window; for a completed game pass a timestamp inside the game.

Input Schema

NameRequiredDescriptionDefault
game_idYesNumeric game id from lolesports-event
starting_timeNoRFC 3339 UTC timestamp whose seconds are divisible by 10; frames begin there

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses meaningful behavior: it describes the returned window, the approximate ten-second frame span, and the possible game_state values. It does not explicitly mention read-only safety, permissions, or rate limits, which keeps it from 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?

The description is front-loaded with the core purpose and then supplies the return fields and starting_time guidance without wasted sentences. Given the amount of return information conveyed, it is appropriately sized.

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 two-parameter retrieval tool with no output schema, the description does a good job explaining what comes back, including team/player metadata, frames, and game_state values. It leaves out edge cases such as invalid timestamps or authorization, so it is complete enough but not exhaustive.

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 schema already documents both parameters well. The description adds useful meaning beyond the schema by explaining that starting_time should be omitted for the latest in-progress window and should be a timestamp inside the game for completed games.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: it returns the lolesports live-stats window for one game, and it names the returned content areas such as patch, team/player metadata, and roughly ten seconds of frames. It is clear what the tool does, but it does not explicitly differentiate itself from nearby siblings such as lolesports_game_details or lolesports_live.

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 description gives clear usage context for the two game states: omit starting_time for the latest window in an in-progress game, and pass a timestamp inside a completed game. It does not name alternative tools or say when not to use this tool, so it falls short of full sibling-routing 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