Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_maps

Read-only

Get 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
gameYesRequired game slug from faceit-games.

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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description goes further by disclosing the upstream 404/NotFound failure mode for unconfigured games and the shape of the returned taxonomy. It does not discuss rate limits, pagination, or caching, so it stops short of a 5.

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 sentences with the purpose front-loaded, the return payload next, and the failure mode last — no filler or repetition. Every sentence contributes a distinct fact an agent would otherwise have to infer.

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 read endpoint with an output schema and clear annotations, the definition covers purpose, prerequisite source for the slug, and the error case. Nothing an agent needs to invoke it correctly is missing.

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% and the single `game` parameter is already documented as a required slug from faceit-games. The description restates that pointer ("discover valid game slugs from faceit-games") but adds no format examples or validation rules beyond the schema, so the baseline 3 applies.

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 opening sentence names a specific verb and resource ("Get FACEIT votable maps for a game") and the second enumerates exactly what the response contains (map id, display name, game map id, class name, image sizes). An agent can tell this is a per-game taxonomy lookup rather than a match, tournament, or clip endpoint, so no sibling differentiation is needed beyond the pointer to faceit-games.

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?

States the usage context (votable maps belonging to one game) and explicitly routes the agent to faceit-games to obtain a valid slug, which is the main prerequisite. It also explains the negative case — a game without map configuration yields upstream 404 surfacing as NotFound — but offers no explicit exclusion of alternatives.

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