Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora.mcp
OverviewDiscussionsAdmin

lolesports_gpr

Read-only

Returns the League of Legends Global Power Rankings: each ranked team with rank, GPR score, Elo, previous rank and change, home league, match and game records, average opponent GPR and the tournaments counted with placements. Provide season (current, or a four-digit Worlds snapshot year such as 2025 or 2024; any season listed in the response is accepted), league (a home league slug from the response's leagues list, for example lck), limit and history (true adds GPR history points). Use it to compare team strength across regions; use lolesports_standings for a tournament's own table.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lolesports_gpr"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional number of teams to return, 1 to 200, best rank first; defaults to all.
leagueNoOptional home league slug from the leagues list of the response, for example lec or lck.
seasonNoOptional ranking snapshot: current (default) or a four-digit Worlds snapshot year such as 2025 or 2024; every season listed in the response's seasons is accepted.
historyNoOptional; true adds each team's GPR history points.

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. Changed1 schema field changed
    • changedInput schema / properties / season / description
      Previous value: -"Optional ranking snapshot: current (default), 2025 (Worlds 2025) or 2024 (Worlds 2024)."New value: +"Optional ranking snapshot: current (default) or a four-digit Worlds snapshot year such as 2025 or 2024; every season listed in the response's seasons is accepted."
  2. Added

TDQS

A4.6/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 real behavior context: the season accepts 'current' or a four-digit Worlds snapshot year, and league slugs must come from the response's leagues list — self-referential discovery guidance that matters operationally. It stops short of mentioning refresh cadence or data lag, so not a 5.

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-loaded with the return contents, then parameter guidance, then the sibling routing — logical order with no filler. The first sentence is a long enumerated run-on, keeping it from a 5, but every clause conveys new 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?

With an output schema present, the description needn't explain return values, yet it still summarizes them helpfully; annotations cover safety; all four params are described in both schema and prose. Nothing an agent needs 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3. The description goes slightly beyond the schema by clarifying that any season listed in the response is valid and that league is example-anchored (lck), which helps the agent construct valid calls on unlisted leagues/years.

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 the League of Legends Global Power Rankings' — and enumerates the returned fields (rank, GPR score, Elo, previous rank and change, home league, records, opponent GPR, tournaments). It names lolesports_standings as the different sibling, so the agent can separate the two without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives the use case ('compare team strength across regions') and the counter-case with a named alternative ('use lolesports_standings for a tournament's own table'). Also states what season values are accepted, removing a likely failure mode.

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