Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

lolesports_tournaments

Read-only

Returns a league's tournaments (splits, seasons, playoffs) newest first with numeric tournament id, slug and start and end dates. Provide league_id from lolesports_leagues. Use a tournament id with lolesports_standings or lolesports_completed_events.

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": {
      "league_id": "<league_id>"
    },
    "name": "lolesports_tournaments"
  }
}

Input Schema

NameRequiredDescriptionDefault
hlNoOptional language code; defaults to en-US.
league_idYesRequired league id from lolesports_leagues.

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

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

Annotations already cover the read-only, open-world safety profile, and the description adds useful context: results are ordered newest first and each entry carries a numeric tournament id, slug, and start/end dates. It omits anything about pagination or whether all tournaments are returned in one call.

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 tight sentences with no waste, and the return shape is front-loaded before the input and follow-up guidance.

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 annotations covering the safety profile, the description gives an agent everything needed to call it correctly and chain the result. Only the relationship to the similarly named seasons tool is left unaddressed.

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. The description's note that league_id comes from lolesports_leagues largely restates the schema text, and the optional hl language parameter is not discussed at all, so it adds little beyond the structured data.

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 league's tournaments) and clarifies the domain meaning by naming the sub-types (splits, seasons, playoffs) plus ordering (newest first). An agent can distinguish this list endpoint from detail endpoints without opening the 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?

Explicitly says to supply league_id from lolesports_leagues and that the resulting tournament id feeds lolesports_standings or lolesports_completed_events, giving clear upstream and downstream routing. It does not, however, say when to choose this over the sibling lolesports_seasons, so there is a small gap.

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