Crawlora MCP

faceit_leaderboard

Read-only

Get FACEIT ranked leaderboard for one game and region. Returns one page of a game region's ranked leaderboard: position, player identity and country, Elo, skill level, verification level and global position. With season set it reads the season-aware ranking and also returns the requested season and the available season history; without season it reads the all-time ranking. The upstream caps a page at 100 rows. An unknown game or region code is a valid empty page, not an error.

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": {
      "game": "<game>",
      "region": "<region>"
    },
    "name": "faceit_leaderboard"
  }
}

Input Schema

Name	Required	Description
`game`	Yes	Required game slug from faceit-games.
`limit`	No	Optional page size, 1-100; the gateway caps a page at 100 rows.
`offset`	No	Optional non-negative row offset.
`region`	Yes	Required region code from faceit-regions, such as EU or NA.
`season`	No	Optional season number; when set the season-aware ranking is read instead of the all-time ranking.

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.

AddedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint the description discloses pagination limits (100 rows per page) and the empty-page-not-error contract, both of which meaningfully change agent behavior. It also explains the dual ranking mode selected by season. Return shape is partly covered, but an output schema already exists so that is not a gap.

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?

Four front-loaded sentences with no filler: purpose and return fields first, then season behavior, then the page cap, then the empty-page edge case. Each sentence earns its place, though the return-field enumeration is somewhat list-like.

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?

For a paginated, filterable read tool with full schema coverage, annotations and an output schema, this covers the decision-relevant behaviors: season mode, page cap, and non-error empties. What remains unsaid (ordering rules, default page size) is minor against the existing structured fields.

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 the schema already documents game, region, limit, offset and season. The description restates the season semantics and the page cap but adds no syntax, format, or edge-case detail beyond what the schema provides; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get FACEIT ranked leaderboard") scoped to one game and region, and enumerates the returned fields. It does not explicitly differentiate itself from faceit_leaderboard_detail or the other leaderboard siblings, which keeps it below a 5.

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 clear conditional guidance: set season for the season-aware ranking, omit it for all-time. It also tells the agent that an unknown game or region yields a valid empty page rather than an error, which prevents needless error handling. It stops short of naming an alternative tool for per-player or detailed lookups.

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.