Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

faceit_leaderboard_detail

Fetch a FACEIT leaderboard's full configuration by ID, including game, region, ranking, scoring, prizes, requirements, status, and visibility rules; unknown IDs return 404.

Instructions

FACEIT leaderboard detail by id. Returns one leaderboard's full configuration: entity references, game and region, group/round/bracket placement, ranking and points configuration, scoring fields, prizes, requirements, status and ranking-field visibility rules. Leaderboard ids come from faceit-championship-search or faceit-standings. An unknown id answers 404.

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": {
      "id": "<id>"
    },
    "name": "faceit_leaderboard_detail"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	24-character leaderboard id from faceit-championship-search or faceit-standings.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the returned fields in detail, states that unknown ids yield a 404, and implies a pure read operation. It omits explicit read-only framing, authentication needs, and rate-limit behavior, which keeps it from 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.

Conciseness5/5

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

Three sentences, front-loaded with the core purpose, then the payload, then id sourcing and error behavior. No filler; each sentence carries distinct information.

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?

There is no output schema, so enumerating the returned configuration fields and the 404 behavior is genuinely necessary and provided. For a single-parameter read tool this is nearly complete, with only auth/permission context 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 coverage is 100% and the single id parameter already documents its 24-character format and source tools. The description's note that ids come from the same two tools largely restates the schema, adding no new format or validation detail, so the 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?

The description opens with a specific verb and resource ("FACEIT leaderboard detail by id") and enumerates the configuration payload the tool returns, so an agent knows exactly what it fetches. It does not explicitly distinguish itself from the sibling faceit_leaderboard, so it falls short of 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?

It tells the agent where valid ids come from (faceit-championship-search or faceit-standings) and what happens on an unknown id (404), which is concrete routing guidance. It stops short of an explicit when-not-to-use statement or a direct contrast with the sibling list tool.

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

Deploy Server