Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_tournaments

Retrieve League of Legends Esports tournaments for a league ID, returning split and season IDs, slugs, and dates newest first for standings or completed-event lookups.

Instructions

League of Legends Esports tournaments. Returns a league's tournaments (splits and seasons) with numeric id, slug, start_date and end_date, newest first. Use a tournament id with lolesports-standings or lolesports-completed-events. An unknown league id returns not found.

Input Schema

NameRequiredDescriptionDefault
hlNoLanguage for names and labels; one of cs-CZ, de-DE, en-US, es-ES, es-MX, fr-FR, hu-HU, ja-JP, ko-KR, pl-PL, pt-BR, th-TH, tr-TR, vi-VN, zh-TW; defaults to en-US
league_idYesNumeric league id from lolesports-leagues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses returned fields (numeric id, slug, start_date, end_date), the ordering ('newest first'), and failure behavior ('an unknown league id returns not found'). Only pagination/response-size behavior is unstated, a minor gap for a read-only listing.

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 the purpose front-loaded, followed by return shape and then downstream usage. Nothing repeats the name or title, and no sentence could be dropped without losing information.

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?

For a two-parameter read tool with no output schema, the description supplies the return fields, ordering, error case, and chaining targets, and the schema covers language defaults. Nothing an agent needs in order to call this correctly is missing.

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 description coverage is 100%, so both league_id and hl are already documented at the field level; baseline 3 applies. The description adds only the failure semantics for an unknown league_id and says nothing about hl beyond what the enum and field description already convey.

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 immediately disambiguates the term by defining it as 'splits and seasons'. An agent can distinguish this from lolesports-leagues and lolesports-seasons without inspecting either 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 routes the agent forward: 'Use a tournament id with lolesports-standings or lolesports-completed-events', and the schema names lolesports-leagues as the source of league_id, so the whole chain is clear. It does not, however, say when to prefer this over a sibling such as lolesports-seasons, which is the one remaining ambiguity.

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

Deploy Server

Other Tools