Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_banlist

Read-only

Get FACEIT public ban list page. Returns one page of the public FACEIT ban list: ban id, banned user id and nickname, avatar, country, reason, start and end timestamps and duration. Paging uses the upstream's size parameter (5-100, default 25) and the opaque cursor returned with the previous page; pass it back to advance. A cursor from the upstream is echoed in the response.

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

Input Schema

NameRequiredDescriptionDefault
sizeNoOptional page size, 5-100; default 25.
cursorNoOptional opaque cursor copied from the previous response; omit for the first page.
reasonNoOptional closed ban reason from faceit-ban-reasons, such as toxicity.

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

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and openWorldHint, so the description focuses on useful behavior. It adds that this returns one page, specifies returned fields, and explains that the upstream cursor is echoed for paging.

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 description is front-loaded with purpose, then concisely covers return fields and paging behavior. There is minor repetition of 'public ban list,' but no significant wasted text.

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

Completeness3/5

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

The tool has an output schema and full schema coverage, reducing what the description must carry. Still, it omits discussion of the reason parameter and related ban-reason tooling, leaving some context incomplete for an agent choosing among siblings.

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%, so the baseline is 3. The description adds paging context for size and cursor, but it does not mention the optional reason filter or how it relates to faceit-ban-reasons.

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?

The description states a specific verb and resource: 'Get FACEIT public ban list page,' and lists the fields returned. It does not explicitly differentiate this from sibling tools such as faceit_banlist_stats or faceit_ban_reasons.

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?

It gives clear paging guidance, including that size and cursor are used to advance pages. However, it does not say when to use this ban list versus related tools like faceit_ban_reasons or faceit_banlist_stats.

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