Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_fpl

Read-only

Get FACEIT Pro League circuits. Returns FPL (FACEIT Pro League) circuits, optionally filtered to one game: circuit id, game and region, display name, default flag, season windows with start and end timestamps, and the configured ranking source. An unknown game is a valid empty list. Paging uses limit and offset and the response reports has_more.

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

Input Schema

NameRequiredDescriptionDefault
gameNoOptional game slug from faceit-games; the upstream answers a missing game with an empty list.
limitNoOptional page size, 1-100; default 20.
offsetNoOptional non-negative row offset.

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
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds useful operational context: the empty-list-on-unknown-game behavior and that paging uses limit/offset with a has_more flag. Beyond that it mostly enumerates return fields, which the output schema already carries, so added behavioral depth is moderate.

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?

Three compact sentences, front-loaded with the core verb and resource, then filtering, then paging. The mid-sentence enumeration of returned fields is a bit list-heavy but still readable and earns its place by conveying result shape.

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?

For a simple read-only, three-optional-parameter lookup with a full output schema and complete schema coverage, the description covers scope, filtering, and paging adequately. It leaves the relationship to related catalog tools implicit, so an agent must infer whether it should call faceit_games first for slugs.

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 schema already defines game, limit, and offset including the empty-list semantics and 1-100 range. The description restates the optional game filter and paging without adding format or edge-case detail beyond the schema, making the baseline 3 appropriate.

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 opens with a specific verb and resource ("Get FACEIT Pro League circuits") and names the exact domain concept, FPL, which none of the listed siblings cover. It does not explicitly contrast itself with adjacent tools like faceit_games or faceit_regions, so it stops short of full sibling differentiation.

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

Usage Guidelines4/5

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

It states the tool works unfiltered or can be narrowed to one game, and points to faceit-games as the source of valid slugs. It also calls out that an unknown game yields a valid empty list, which prevents wasted retries. There is no explicit when-not guidance or named alternative for related lookups.

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