Crawlora MCP

faceit_championship_search

Read-only

Get discover FACEIT championships and leaderboards. Returns leaderboard discovery rows, which are the anonymous way to discover championship ids: leaderboard identity, entity id/type, game and region, season, group/round/bracket placement, ranking type, scoring fields, dates, status and prize metadata. Defaults to ongoing championships. status is a closed enum (see faceit-leaderboard-statuses); entity_type and type are forwarded as filters and are not server-validated. The upstream caps a page at 100 rows.

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": "faceit_championship_search"
  }
}

Input Schema

Name	Required	Description
`game`	No	Optional game slug from faceit-games.
`type`	No	Optional leaderboard type; defaults to championship and normally equals entity_type.
`limit`	No	Optional page size, 1-100; default 25.
`offset`	No	Optional non-negative row offset.
`status`	No	Optional status from faceit-leaderboard-statuses; defaults to ONGOING.
`country`	No	Optional two-letter ISO country filter such as DE.
`subtype`	No	Optional leaderboard subtype filter.
`has_drops`	No	Optional drops filter.
`entity_type`	No	Optional entity type; defaults to championship. Documented values: championship, hub, tournament, league, club, matchmaking (the gateway does not validate this filter).

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.8/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses that the upstream caps a page at 100 rows, that results default to ONGOING status, and that entity_type/type are forwarded unvalidated — real operational caveats an agent needs. It does not discuss rate limits or error behavior, but the read-only safety profile is already covered by annotations.

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

Conciseness3/5

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

The purpose and the useful constraints come first, but the long mid-sentence enumeration of return fields (identity, entity id/type, game, region, season, placement, scoring, dates, status, prize) is largely redundant given an output schema exists. Tightening that run-on list would sharpen the definition.

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 9-parameter, no-required-filter discovery tool with an output schema and annotations, the description covers the key missing pieces: default status, page-size ceiling, and unvalidated filter forwarding. Only explicit sibling routing and pagination semantics beyond the 100-row cap are absent.

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%, so every parameter is already documented with defaults and constraints. The description restates defaults and the unvalidated-filter caveat that the schema itself already contains, adding no new meaning beyond the structured fields.

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 discover FACEIT championships and leaderboards') and clarifies the return shape is leaderboard discovery rows used to obtain championship ids, which implicitly separates it from the single-championship sibling. It never names that sibling explicitly, so the differentiation is inferred rather than stated.

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 a clear usage cue ('the anonymous way to discover championship ids') and notes the default of ongoing championships, which tells the agent what it gets without filters. It stops short of explicit when-not-to-use guidance or naming alternatives like faceit_championship for detail 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.