Skip to main content
Glama

faceit_championship_participants

Read-only

Get 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

NameRequiredDescriptionDefault
idYesRequired championship UUID.
limitNoOptional page size, 1-50.
offsetNoOptional non-negative row offset.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, open-world operation. The description adds useful behavior beyond that: the 50-item upstream page cap, limit/offset paging, echoed start/end markers, and the main fields returned. It does not cover error behavior or rate limits, but it meaningfully improves transparency.

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 definition is front-loaded with the core action and then adds pagination and return-shape details efficiently. The field enumeration is useful but somewhat redundant given the output schema, so it stops short of maximal conciseness.

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?

Because an output schema exists, the description does not need to fully document response values. It covers the key complexity points for this tool: paging, the page-size cap, and the participant payload domain. Missing edge-case or error guidance is a minor gap for a read-only participant 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%, and the schema already documents the required championship UUID, limit range, and non-negative offset. The description repeats the 50-item cap and paging model but adds little parameter meaning beyond what the schema already provides.

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 states a specific verb and resource: get a FACEIT championship participants page. It clearly scopes the result to one page of participants, but it does not explicitly distinguish this tool from nearby siblings such as championship details, bracket, or championship search.

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?

The intended use is implied: fetch participant data for a given championship. There is no explicit when-to-use, when-not-to-use, or guidance pointing to sibling alternatives for championship metadata, brackets, or search.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.