Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_regions

Retrieve documented and observed FACEIT region codes, including GEO-REGION values and live ranking or championship region codes, for validating or forwarding region inputs.

Instructions

FACEIT region codes known to the website. Returns the documented region values: the website client's GEO-REGION list, region codes observed serving live ranking data, and free-form region values seen on live championship leaderboard rows. Region is not a server-validated closed set, so this list is advisory and any well-formed 2-8 character code is forwarded to the upstream.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does substantial work: it discloses that region is not a server-validated closed set, that the list is advisory and compiled from three distinct sources, and that arbitrary well-formed codes pass through. It does not say whether the list is static or fetched live, which is the main remaining gap.

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?

Two sentences, front-loaded with the resource name and immediately followed by the return contents and the caveat. Dense but every clause carries information; no filler or restatement of the tool name.

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 parameterless reference lookup with no output schema, the description covers what the values are, where they come from, and that they are non-authoritative. Only the freshness/source-of-truth question (static snapshot versus live fetch) is unanswered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description still adds useful constraint semantics for downstream usage by stating the accepted code format is 2-8 characters and that the values are not enforced.

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?

Names a specific resource (FACEIT region codes) and specifically says what the returned set contains: the client's GEO-REGION list, codes observed in live ranking data, and free-form values from championship leaderboard rows. It does not explicitly contrast itself with the sibling region lookup (bbb_regions), so it falls 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 rather than stated: the description makes clear the list is advisory and 'any well-formed 2-8 character code is forwarded to the upstream', which tells an agent it need not restrict itself to the returned values. There is no explicit when-to-use/when-not-to-use statement or named alternative.

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