Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_game_modes

Retrieve FACEIT public matchmaking queues for a game and region, returning queue IDs, localized labels, spectator flags, and team sizes to map available play modes.

Instructions

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

NameRequiredDescriptionDefault
gameYesGame slug, one of the values returned by faceit-games.
regionYesRegion code such as EU; see faceit-regions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.6/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 burden and does reasonably well: it discloses the full return shape, that both inputs are required upstream, and that a non-existent pair returns an empty list rather than an error. It omits auth/rate-limit expectations, but for a read-only public listing endpoint that is a minor gap.

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?

Front-loaded and short, but the first sentence ('FACEIT public queues for a game and region') is nearly fully restated by the opening of the second sentence, so one of three sentences is close to redundant. The remaining content is efficient.

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 and no annotations, so the description must supply the return shape and it does so by listing the fields. Combined with the required-input and empty-list semantics, an agent has enough to invoke and interpret the result; only auth/precondition context is 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 description coverage is 100% and the game parameter is a full enum, so the schema already documents both parameters, including the pointer to faceit-games for slugs and faceit-regions for region codes. The description only restates that both are required, adding no syntax or format detail beyond the schema, 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?

States a specific verb and resource ('Returns the public matchmaking queues for a game and region') and enumerates the returned fields (queue id, queue group id, label, spectator flag, team size). It is clear what the tool does, though it does not distinguish itself from any FACEIT sibling (e.g., faceit-championship or faceit-games), so it stops 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 Guidelines3/5

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

Usage is implied: call it when you need the public queues for a given game/region pair. The description adds a useful edge-case rule (empty list is valid, not an error) and notes both parameters are mandatory upstream, but it gives no explicit when-not-to-use or pointer to an alternative queue-related tool.

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

Deploy Server

Other Tools