Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_standings

Read-only

Get FACEIT championship standings by group and round. Returns a championship's standings for one group and round: the leaderboard identity and each ranked participant's entity id, name, avatar, skill level, country, played count, position and points. The upstream requires group and round plus a segment or match number. An entity or round without standings is a valid empty list, not an error.

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": {
      "entity_id": "<entity_id>",
      "group": "<group>",
      "round": "<round>"
    },
    "name": "faceit_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesRequired group number.
matchNoOptional match number; provide segment or match.
roundYesRequired round number, or a comma-separated list such as 1,2.
segmentNoOptional segment number; provide segment or match.
entity_idYesRequired championship UUID.

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

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses a genuinely useful trait: an entity or round with no standings returns a valid empty list rather than an error. It also sketches the returned payload (leaderboard identity, participant fields), though with an output schema present that part is mostly redundant.

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 scope constraint and ending on the empty-result caveat; nothing extraneous. There is mild redundancy between the opening 'Get ... by group and round' and the following 'Returns ... for one group and round'.

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?

Covers the required and conditional parameters, the empty-list edge case, and the shape of the result for a five-parameter read tool. Return-value detail is partly unnecessary given the output schema, but nothing an agent needs in order to call it correctly is missing.

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 would be 3, but the description adds a cross-field rule the schema does not convey: segment or match must accompany group and round even though both are optional/nullable in the schema. That constraint meaningfully reduces the chance of a malformed call.

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 ('Get FACEIT championship standings') plus the scoping dimensions (group and round), which an agent can match to a concrete need. It doesn't name a sibling to distinguish itself from faceit_championship_participants or faceit_championship_bracket, so differentiation relies on the tool name alone.

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?

The description clarifies a real calling condition – that group and round are needed together with a segment or match number – which guides invocation. It gives no guidance on when to prefer this over the closely named sibling tools (bracket, participants, championship), so selection between them is left to inference.

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