Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

faceit_ban_reasons

Returns the closed set of FACEIT ban reasons used to filter the ban list via faceit-banlist, so you can pick a server-validated value instead of guessing.

Instructions

FACEIT ban reason enum. Returns the closed ban-reason enum the ban-list filter accepts. The upstream names these values in its own validation error, so they are server-validated. Pass one as the reason parameter of faceit-banlist to filter the ban list.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose two meaningful traits: the enum is 'closed' and the values are server-validated because upstream echoes them in its own validation error. That tells the agent the list is authoritative and exhaustive. It does not state whether this is a cached/static lookup or a live call, which is the only remaining behavioral gap for a zero-parameter read.

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 short sentences, front-loaded with the resource and its closed-set nature, then the validation rationale, then the concrete usage. No filler and no repetition of the title.

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, so the description must convey the return value, and it does ('closed ban-reason enum'). It stops short of stating the concrete shape (e.g. array of strings vs. objects), which is the one thing an agent might still want.

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?

There are no parameters, so the schema contributes nothing and the baseline is 4. The description correctly avoids restating parameter semantics and instead spends its words on the return value's role.

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 description uses a specific verb and resource ('Returns the closed ban-reason enum') and immediately scopes it to what the ban-list filter accepts. This clearly distinguishes it from the many data-fetching siblings, none of which return an enum of filter values.

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?

It gives the exact downstream usage: 'Pass one as the reason parameter of faceit-banlist to filter the ban list.' The consuming tool and parameter are named, so the agent knows both when to call this and what to do with the result.

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

Deploy Server