Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_gpr

Retrieves League of Legends Esports Global Power Rankings with team ranks, GPR scores, Elo, records, and tournament placements; filter by season or home league and add daily history.

Instructions

League of Legends Global Power Rankings. Returns the League of Legends Esports Global Power Rankings (GPR): every ranked team with rank, GPR score, Elo, previous rank and rank change, home league, match and game records, average opponent GPR and the tournaments counted with each result and placement. season selects current (the running year, default) or the Worlds snapshot of a four-digit year (2025, 2024; every season listed in the response's seasons is accepted, and a year without a snapshot returns 404); league keeps one home league's teams and history adds the daily GPR history points. The response lists the seasons and home leagues available.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of teams to return, 1 to 200, best rank first; defaults to all
leagueNoHome league slug from the leagues list of the response, for example lck
seasonNoRanking snapshot; current, or a four-digit Worlds snapshot year such as 2025 or 2024 (any season listed in the response is accepted); defaults to current
historyNoAdd each team's GPR history points

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden and does well: it discloses the default season, the 404 failure mode for years without a snapshot, that the response self-describes available seasons and leagues, and that history adds daily points. Missing: whether limit applies before or after league filtering, and any auth/rate-limit/pagination notes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the resource and return payload before any parameter talk, and every sentence carries information. It is dense and somewhat long for a single paragraph, but no sentence is redundant 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 no output schema and no annotations, the description compensates by enumerating the response payload, defaults, and error behavior for each parameter. Remaining gaps are ordering/limit interaction with league filtering, which the schema partially covers.

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 descriptions largely mirror the schema text ('current, or a four-digit Worlds snapshot year such as 2025 or 2024'). The description adds minor value — clarifying that 'current' means the running year and that history yields daily GPR points — but not enough to exceed baseline for fully documented parameters.

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?

Names the exact product ('League of Legends Esports Global Power Rankings') and enumerates the returned fields — rank, GPR score, Elo, previous rank, rank change, home league, records, opponent GPR, tournaments. That is a specific verb+resource, clearly distinct from sibling lolesports tools like standings, teams, or leagues.

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?

Explains how to choose season ('current' default vs a four-digit Worlds snapshot year), when a year returns 404, and that league narrows to one home league's teams. It gives clear usage context and discovery hints (the response lists valid seasons and leagues), but never names an alternative sibling tool or states when not to use it.

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