Crawlora MCP

lolesports_completed_events

Read-only

Returns every completed match of one League of Legends tournament with final game wins plus game ids and VOD references per game. Provide tournament_id from lolesports_tournaments. An empty list is valid for a tournament that has not started; prefer lolesports_standings for rankings.

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": {
      "tournament_id": "<tournament_id>"
    },
    "name": "lolesports_completed_events"
  }
}

Input Schema

Name	Required	Description	Default
`hl`	No	Optional language code; defaults to en-US.
`tournament_id`	Yes	Required tournament id from lolesports_tournaments.

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/5.0

Behavior3/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 one genuinely useful behavioral fact — an empty list is a valid result for an unstarted tournament — but much of the return-content wording (game wins, game ids, VODs) duplicates what the output schema already provides.

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 sentences, front-loaded with the return contract, then the required input, then the edge case and alternative route. No filler.

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 and full parameter documentation, the description supplies the missing pieces an agent needs: input provenance, empty-result semantics, and the alternative tool for rankings. Minor gap is that it never mentions the 'hl' parameter or whether results are paginated.

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% and the schema itself already says tournament_id comes from lolesports_tournaments, so the description's provenance hint adds little. The optional 'hl' language parameter is not mentioned in the description at all.

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 every completed match of one League of Legends tournament') plus what is included (final game wins, game ids, VOD refs), which distinguishes it from lolesports_schedule and lolesports_event that a sibling-only view would confuse it with.

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?

Explicitly says where tournament_id comes from (lolesports_tournaments) and routes ranking queries to lolesports_standings. It doesn't address the other plausible alternatives (schedule, event, game_window) for live/upcoming matches, so it stops short of full when/when-not coverage.

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?