Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

lolesports_game_details

Read-only

Returns per-player detail frames for one League of Legends game: level, KDA, gold, creep score, kill participation, damage share, wards, attack damage, ability power, armor, magic resistance, items, rune ids and skill order. Provide game_id from lolesports_event; optionally restrict participant_ids (1 to 10 joined by underscores, from lolesports_game_window metadata). starting_time follows the same ten-second rule as lolesports_game_window.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "game_id": "<game_id>"
    },
    "name": "lolesports_game_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
game_idYesRequired game id from lolesports_event games.
starting_timeNoOptional RFC 3339 UTC timestamp with seconds divisible by 10; frames start there.
participant_idsNoOptional participant ids joined by underscore, for example 1_2_3, to limit player rows; omit for all ten players.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine behavioral context beyond that: results are frame-based (ten-second granularity anchored at starting_time) and row scope is capped at ten players, optionally narrowed by participant_ids. It stops short of describing volume or pagination for long games.

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?

Three sentences, front-loaded with the return payload and followed by parameter sourcing rules; no filler. The long stat enumeration is somewhat redundant given an output schema exists, which keeps it from a 5.

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?

With an output schema present, the description does not need to explain return values, and it instead spends its space on the input sourcing chain and frame semantics — the parts an agent actually needs. Nothing critical is missing for a read-only lookup keyed by game_id.

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?

Schema coverage is 100%, so all three parameters are already documented, including the underscore-joined format and the ten-second divisibility rule. The description's added value is provenance (game_id from lolesports_event, participant_ids from lolesports_game_window metadata), which edges above a pure restatement but stays near baseline.

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 League of Legends game' — and enumerates the stats contained. The reference to lolesports_game_window's ten-second rule implicitly contrasts this with the frame-level sibling, so the agent can tell which tool serves per-player detail versus window metadata.

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 a clear prerequisite chain: game_id must come from lolesports_event, and participant_ids optionally from lolesports_game_window metadata. It does not explicitly state when to prefer this over lolesports_game_window or what to do when participant ids are unknown, but the sourcing guidance is concrete enough to drive correct calls.

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

All Crawlora MCP toolsInspect
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