Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

faceit_championship_participants

Fetch paginated participant records for a FACEIT championship, returning membership IDs, player profiles, roles, and status.

Instructions

FACEIT championship participants page. Returns one page of a championship's participants: membership id, player identity (id, nickname, avatar, country and game list), the championship reference, role names and the participant's championship status. The upstream caps the page size at 50. Paging uses limit and offset, and the response echoes the upstream start and end markers.

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_championship_participants"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Championship UUID from faceit-championship-search.
`limit`	No	Optional page size, 1-50; default 20.
`offset`	No	Optional non-negative row offset.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the upstream hard cap of 50 rows per page, the limit/offset paging mechanism, and that the response echoes upstream start/end markers. It omits error behavior for an invalid or non-existent championship id and any permission or rate-limit considerations.

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?

The first sentence establishes identity and scope up front, followed by the return payload and then paging constraints. The field enumeration is long but earns its place because no output schema exists; nothing is redundant or throat-clearing.

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 simple three-parameter read tool with no output schema, the description covers payload shape, paging contract, and the upstream size cap, which is what an agent needs to call it correctly. Only error and empty-result behavior are unaddressed.

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 limit (1-50, default 20), offset, and the required id are already documented in the schema. The description restates the 50-item cap and limit/offset paging but adds no format or interpretation detail beyond it, 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 names a specific verb and resource: it returns one page of a championship's participants, and enumerates exactly what each participant record contains (membership id, identity, championship reference, role names, status). This clearly separates it from faceit_championship and faceit_championship_bracket, though it never explicitly contrasts those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it lists participants of a known championship, and the schema notes the id comes from faceit-championship-search. There is no explicit when-to-use versus when-not statement, no guidance on when to page through the whole roster versus stopping, and no named alternative for other championship data needs.

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

Deploy Server