Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

faceit_leaderboard

Fetch a FACEIT ranked leaderboard for a game and region, including positions, players, Elo, skill level, and verification; add a season for season-aware rankings or omit it for all-time results.

Instructions

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	Game slug, one of the values returned by faceit-games.
`limit`	No	Optional page size, 1-100; default 20 and the gateway caps a page at 100 rows.
`offset`	No	Optional non-negative row offset.
`region`	Yes	Region code such as EU or NA; see faceit-regions.
`season`	No	Optional season number; when set the season-aware ranking is read.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it discloses non-obvious behavior well: the upstream caps a page at 100 rows, unknown game or region codes yield a valid empty page rather than an error, and setting season also changes what is returned (season and season history). It says nothing about authentication, rate limits, or sort order, which are the remaining gaps for a read-only feed with no annotation cover.

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 sentences, front-loaded with what the tool returns, then pagination and the season branch, then the empty-page caveat. Every sentence contributes. The row-field enumeration is slightly long but justified because there is no output schema.

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 does the necessary work: it enumerates returned fields, explains pagination limits, and clarifies season-dependent return shape. Only ordering of the leaderboard and any auth expectations are unstated, which are minor for a public ranked listing.

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 all five parameters are already documented, including the 1-100 limit, non-negative offset, and season semantics; the baseline is therefore 3. The description reinforces the page cap and the season branch but adds no syntax, format, or validation detail the schema lacks.

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?

The description names a specific resource and scope: a FACEIT ranked leaderboard for exactly one game and one region, returning one page of ranked rows. That is far more precise than a title restatement. It does not, however, distinguish itself from near-named siblings like faceit_leaderboard_detail or faceit_leaderboard_statuses, so an agent must infer the boundary from the names alone.

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?

It gives an explicit branch condition: with season set, read the season-aware ranking; without season, read the all-time ranking. That is real when-to-use guidance. It stops short of naming an alternative tool or stating when not to use this one (e.g., for a single player's standing), leaving the sibling choice to inference.

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

Deploy Server