Crawlora MCP

faceit_game_modes

Read-only

Get FACEIT public queues for a game and region. Returns the public matchmaking queues for a game and region: queue id, queue group id, localized label, spectator flag and team size. Both game and region are required by the upstream. A pair with no queues is a valid empty list, 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_game_modes"
  }
}

Input Schema

Name	Required	Description	Default
`game`	Yes	Required game slug from faceit-games.
`region`	Yes	Required region code from faceit-regions.

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

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral detail: the exact fields returned (queue id, queue group id, localized label, spectator flag, team size) and the crucial semantics that an empty list is success, which prevents an agent from treating zero results as an error or retrying. Rate limits and failure modes beyond the empty case are not discussed.

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 leading sentence carries the core purpose and is front-loaded correctly. The second sentence repeats "public matchmaking queues for a game and region" from the first, which is mild redundancy, but the remaining clauses (required params, empty-list semantics) each earn their place.

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 an output schema present, the description is not obliged to enumerate return fields, yet it does so briefly alongside the empty-result rule, making the contract clear. For a two-parameter read-only lookup, nothing essential about invocation is missing; only upstream limits or error 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% and both parameters carry their own descriptions pointing at faceit-games and faceit-regions, so the baseline is 3. The description's restatement that both are "required by the upstream" adds little beyond the schema's required array; it does not expand on slug format or region code casing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get FACEIT public queues for a game and region" names a specific verb (get), a specific resource (public queues), and the two scoping dimensions. It is immediately distinguishable from the FACEIT siblings (faceit_ban_reasons, faceit_banlist), which deal with bans rather than queues.

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?

The description establishes clear usage context: both game and region are mandatory and must be supplied together, and a no-queue result is a legitimate outcome rather than a failure. It does not name a when-not condition or an alternative tool, but no overlapping sibling exists, so the practical guidance gap is small.

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.