Crawlora MCP

lolesports_standings

Read-only

Returns one League of Legends tournament's stages with bracket or round-robin matches and ordered team rankings with win-loss records. Provide tournament_id from lolesports_tournaments. Playoff matches carry previous_match_ids linking bracket rounds; rounds=true adds section ids, types and the named bracket rounds. Use match ids with lolesports_event.

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_standings"
  }
}

Input Schema

Name	Required	Description
`hl`	No	Optional language code; defaults to en-US.
`rounds`	No	Optional; true adds each section's id and type (group or bracket) and bracket round names with their match ids, from a second upstream call.
`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.

Changed1 schema field changedOct 29, 2026

addedInput schema / properties / rounds

Added value: +{
+  "description": "Optional; true adds each section's id and type (group or bracket) and bracket round names with their match ids, from a second upstream call.",
+  "type": "boolean"
+}

AddedOct 28, 2026

TDQS

A4.2/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 genuinely non-obvious behavior: playoff matches carry previous_match_ids linking bracket rounds, and rounds=true triggers a second upstream call — useful cost/latency signal an agent would otherwise not expect.

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?

Four sentences, front-loaded with what is returned, then the input source, then the optional flag's effect, then the downstream tool. No filler or restated title.

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?

An output schema exists, so return-value detail is not required, yet the description still sketches the payload shape (stages, matches, rankings, previous_match_ids). Only the hl language parameter's effect goes unmentioned, a minor gap for an otherwise self-contained definition.

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 rounds flag's second-call behavior. The description restates the rounds semantics and the tournament_id source but adds nothing on syntax or format, and never mentions the hl language parameter; baseline 3 is appropriate.

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 a single LoL tournament's stages, bracket/round-robin matches, and ordered team standings with win-loss records. That is far more precise than the sibling lolesports_tournaments (which lists tournaments) and lolesports_event (which fetches one match), so an agent can distinguish it without opening a schema.

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 concrete prerequisite chain ('Provide tournament_id from lolesports_tournaments') and a downstream routing hint ('Use match ids with lolesports_event'), which covers the common workflow. It stops short of an explicit exclusion, e.g. when to prefer lolesports_schedule or lolesports_seasons instead, so it is clear context rather than a full when/when-not rule set.

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?