Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_skill_levels

Retrieve a game's FACEIT skill-level configuration, including levels 1–10 and their inclusive Elo bands, to map ranking rows to skill levels.

Instructions

FACEIT skill levels and Elo bands for a game. Returns a game's skill-level configuration: the level number (1-10) and its inclusive Elo band. This is the discovery surface for the skill levels that ranking rows report. The upstream returns a default mapping for any slug, so this route does not prove a game exists and is not an error for an unknown-but-valid slug.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "game": "<game>"
    },
    "name": "faceit_skill_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesGame slug, one of the values returned by faceit-games.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the return shape (level number plus inclusive Elo band) and the important behavioral quirk that unknown-but-valid slugs return a default mapping rather than an error. It does not mention ordering, pagination, or auth, but for a small lookup endpoint the key non-obvious behavior is covered.

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 sentences, front-loaded with the purpose and return shape, followed by positioning and then the caveat. Nothing is redundant, though the 'discovery surface' phrasing is a little dense compared to a plain statement of what it resolves.

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?

One enum parameter, no output schema, no annotations — the description covers purpose, return contents, and the fallback-mapping behavior. What is left implicit is the result's structure (single object vs list of ten levels) and whether the ordering is guaranteed, which would help an agent parse the response without guessing.

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?

Schema coverage is 100% and the enum already constrains the game slug, so the baseline is 3. The description still adds meaning beyond the schema by explaining that the slug does not need to correspond to a real game because a default mapping is returned, which changes how an agent should interpret the parameter's validity.

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 names a specific resource (FACEIT skill levels and Elo bands for a game) and states exactly what is returned: the level number 1-10 with its inclusive Elo band. It also positions itself relative to other surfaces ('the discovery surface for the skill levels that ranking rows report'), so an agent can tell it apart from faceit_player_rank or faceit_games without opening the schema.

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 gives clear context for when this tool is the right call — resolving what the level numbers in ranking rows mean. The caveat that the upstream returns a default mapping for any slug, so the call does not prove a game exists, is useful usage guidance. It stops short of naming an alternative (e.g. faceit_games) for validating a slug, so there is no explicit when-not routing.

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

Deploy Server

Other Tools