Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_maps

Retrieve a game's FACEIT votable map taxonomy, including map IDs, display names, class names, and image sizes. Supply a valid game slug; games without map configuration return NotFound.

Instructions

FACEIT votable maps for a game. Returns a game's votable map taxonomy: map id, display name, game map id, class name and two image sizes. A game without map configuration is answered with 404 by the upstream and surfaces as NotFound; discover valid game slugs from faceit-games.

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

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

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

With no annotations present, the description carries the burden and does so well: it discloses the shape of the response payload and, notably, the upstream 404 behavior and how it surfaces as NotFound, which is exactly the kind of error semantics an agent needs. It does not mention auth requirements, rate limits, or caching, leaving a modest gap for a mutation-free read tool.

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 tight sentences: purpose first, payload second, failure/derivation third. Every clause earns its place — the return-field list substitutes for an absent output schema, and the 404 note is actionable rather than filler.

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

Completeness5/5

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

For a one-parameter lookup with no output schema and no annotations, the description covers purpose, return values, error behavior, and parameter derivation. An agent has everything needed to call it correctly and to interpret a NotFound.

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 single parameter is a 27-value enum already documented, so the baseline would be 3. The description adds real meaning beyond the schema by pointing at faceit-games as the source of valid slugs and by explaining what happens when a slug has no map configuration.

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 verb and resource ("Returns a game's votable map taxonomy") and enumerates the returned fields (map id, display name, game map id, class name, two image sizes). No sibling in the list covers FACEIT map taxonomy, so the agent can confidently distinguish this tool from faceit_ban_reasons, faceit_championship, and others without opening a 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 states the prerequisite clearly: valid game slugs come from faceit-games, which tells the agent to call that tool first. It also gives a conditional failure rule (a game without map configuration yields upstream 404 surfaced as NotFound). What is missing is any explicit "do not use this for X" exclusion, but for a single-resource lookup tool the context is sufficient.

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