Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

lolesports_event

Read-only

Returns one League of Legends match: league, tournament, teams, best-of format, and every game with its id, number, state, blue and red side assignment and VODs, plus broadcast streams. Provide match_id from lolesports_schedule, lolesports_live or lolesports_standings. Use a game id with lolesports_game_window or lolesports_game_details.

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": {
      "match_id": "<match_id>"
    },
    "name": "lolesports_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
hlNoOptional language code; defaults to en-US.
match_idYesRequired match id from lolesports_schedule, lolesports_live or lolesports_standings.

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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral context about the returned data and the required upstream identifiers, though it does not discuss rate limits or failure behavior; with annotations present and an output schema, 4 is appropriate.

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 return contents, then immediately gives the required id source and alternatives. Every sentence contributes actionable information with no filler.

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?

With annotations, a fully described two-parameter schema, and an output schema, the description supplies everything an agent needs: what the tool returns, how to get the required match_id, and where to go for game-level data. No meaningful gaps remain.

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 both parameters are already documented in the input schema. The description reinforces where match_id comes from but does not add syntax, format, or other meaning beyond the schema descriptions. Baseline 3 is correct.

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 one League of Legends match') and enumerates exactly what the response contains: league, tournament, teams, best-of format, per-game details, and broadcast streams. It clearly distinguishes itself from the game-level siblings by pointing to game ids for lolesports_game_window and lolesports_game_details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent where to obtain the required match_id (lolesports_schedule, lolesports_live, lolesports_standings) and names the alternative tools to use when the agent has a game id instead. This is clear when-to-use and sibling-routing guidance.

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