Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_regions

Read-only

Get FACEIT region codes known to the website. Returns the documented region values: the website client's GEO-REGION list plus region codes observed serving live ranking data. 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. Use it before calling faceit_leaderboard or faceit_player_rank so the region code is one the website actually uses.

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

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

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only and open-world behavior, but the description adds a genuinely non-obvious trait: the region set is not server-validated, the list is advisory only, and any well-formed 2-8 character code is forwarded upstream. This corrects the natural but wrong assumption that the returned list is an exhaustive enum. It stops short of describing rate limits or caching, a minor gap for a static lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose, then provenance of the values, then the routing instruction. Each sentence carries distinct information: what is returned, why the list is not authoritative, and when to call it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and an output schema present, the description needs only to explain purpose and caveats, both of which it does. The advisory nature of the list is exactly the context an agent would otherwise lack.

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 nonetheless supplies the downstream region-code format constraint (2-8 characters) that an agent needs when composing calls to the sibling tools, which is useful though not parameter documentation for this tool itself.

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?

The first sentence states a specific verb and resource: retrieving FACEIT region codes known to the website. The second sentence clarifies what the returned values actually are (GEO-REGION list plus codes observed serving live ranking data), which distinguishes this tool from the leaderboard/rank siblings that merely consume those codes.

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

Usage Guidelines5/5

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

The final sentence gives an explicit when-to-use rule and names the two consumers it should precede: faceit_leaderboard and faceit_player_rank. It also explains why the lookup matters (so the code is one the website actually uses), leaving nothing to inference.

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

All Crawlora MCP toolsInspect
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.

Resources