Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_rules

Read-only

Get FACEIT published competition rules. Returns one page of the published FACEIT competition rule sets: rule id, name, game, organizer id, creation and update timestamps and the full rule body in markdown. The upstream accepts entity filters but ignores them, so this route exposes only paging. Paging uses limit and offset.

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

Input Schema

NameRequiredDescriptionDefault
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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely non-obvious behavior: the upstream accepts entity filters yet silently ignores them, so the route exposes paging only. It also discloses the return granularity (one page) and that the rule body arrives as full markdown, which matters for downstream handling.

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?

Four short sentences, front-loaded with purpose and then the paging caveat, with no filler. The field enumeration in sentence two is somewhat redundant given an output schema exists, but it is compact and does not obscure the key operational point.

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 read-only, two-parameter list tool with full schema coverage and an output schema, the description covers the essential operational quirk (ignored filters, paging only) and return granularity. The only gap is the absence of routing guidance against other rules-oriented siblings, which is minor here.

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% (limit 1-100 default 20, non-negative offset), so the schema already carries parameter meaning. The description only restates that paging uses limit and offset, adding no format or interaction detail beyond that baseline.

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?

States a specific verb and resource ("Get FACEIT published competition rules") and immediately scopes it to "one page of the published FACEIT competition rule sets," enumerating the returned fields. An agent can distinguish this from the other faceit_* tools (ban reasons, championships, leaderboards) without opening any schema.

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 note that entity filters are ignored and only paging is exposed tells the agent how to call it, but there is no explicit when-to-use/when-not guidance or named alternative. The agent must infer that this is the sole route for published rule text.

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