Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_player_rank

Read-only

Get FACEIT player ranked position in one game and region. Returns one player's position in a game and region ranking, either the all-time ranking or a season-aware ranking when season is set. A nickname is resolved to its user id first, so a nickname request costs one extra upstream lookup. Position is null when the player has no rank there. Exactly one of nickname and user_id is required.

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>",
      "region": "<region>"
    },
    "name": "faceit_player_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesRequired game slug from faceit-games.
regionYesRequired region code from faceit-regions.
seasonNoOptional season number; when set the season-aware ranking is read.
user_idNoOptional FACEIT user UUID; exactly one of nickname and user_id is required.
nicknameNoOptional FACEIT nickname; exactly one of nickname and user_id is required.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-dependency profile is covered. The description adds real behavioral context beyond that: the extra upstream lookup for nickname resolution and the null-position case for unranked players. It stops short of describing rate limits or how the ranking is sourced/updated, so it is solid but not rich.

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?

Front-loaded with the core action and only four sentences, each carrying information. The second sentence partially restates the first ('Returns one player's position in a game and region ranking'), which is the only real redundancy.

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?

With 5 parameters, full schema coverage, an output schema, and read-only annotations, the remaining burden on the description is small and it meets it: identity requirement, season semantics, null-result behavior, and the cost of nickname resolution are all covered.

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%, so the baseline is 3, but the description earns a bump by explaining the consequence of choosing nickname over user_id (one extra lookup) and by clarifying that season toggles which ranking is read rather than just filtering output. The game/region and exactly-one-of constraints restate the schema rather than adding to it.

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?

States a specific verb and resource: fetching one FACEIT player's ranked position within a given game and region. The phrase 'Returns one player's position in a game and region ranking' implicitly separates it from board-level siblings like faceit_leaderboard, but no sibling is named, so an agent must infer the boundary.

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?

Gives concrete selection guidance: set 'season' for season-aware ranking versus all-time, and use either nickname or user_id. It also flags the cost tradeoff (nickname triggers an extra upstream lookup), which is genuinely useful routing advice, though it never states when to prefer a different tool.

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