Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_game_details

Fetch per-player detail frames for a League of Legends Esports game, including level, KDA, gold, creep score, damage share, wards, items, runes, and skill order using game and participant IDs.

Instructions

League of Legends Esports player game details. Returns per-player detail frames for one game: level, KDA, gold, creep score, kill participation, damage share, wards, attack damage, ability power, armor, magic resistance, final items, rune ids and skill order. Use participant ids from lolesports-game-window metadata. The same starting_time rule as lolesports-game-window applies.

Input Schema

NameRequiredDescriptionDefault
game_idYesNumeric game id from lolesports-event
starting_timeNoRFC 3339 UTC timestamp whose seconds are divisible by 10; frames begin there
participant_idsNoParticipant numbers 1 to 10 joined by underscores, for example 1_2_3

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?

No annotations are provided, so the description carries the full burden. It usefully discloses the returned field set and the cross-tool dependency, but says nothing about what happens when the optional starting_time is omitted (default start?), whether all participants are returned by default, or rate/limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two front-loaded sentences plus a one-line cross-reference; the return-field enumeration is dense but informative. Slight redundancy between the field list and 'player game details' heading, but no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description must do more work; it does list returned fields and the upstream dependency, but leaves unresolved what the optional parameters default to and whether results are scoped to all players.

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 baseline is 3, and the description adds genuine context beyond the schema by naming the source of participant ids and pointing at the shared starting_time rule. It stops short of explaining default/omission behavior for the optional parameters.

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 and resource (returns per-player detail frames for one game) and enumerates the exact stat categories returned. The mention of lolesports-game-window as the source of participant ids makes its distinct role clear relative to that sibling.

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?

Gives the key prerequisite: participant ids come from lolesports-game-window metadata, and the same starting_time rule applies there. It does not explicitly state when to prefer this over lolesports_game_window (e.g., frames vs. metadata) or any exclusions, so it falls short of a full when/when-not treatment.

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