Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_leaderboard_statuses

Returns the exact uppercase FACEIT leaderboard status values—ONGOING, UPCOMING, and FINISHED—plus observed entity and leaderboard type values, so callers can avoid rejected lowercase or invalid inputs.

Instructions

FACEIT leaderboard status enum. Returns the closed leaderboard status enum: ONGOING, UPCOMING and FINISHED. The upstream rejects lowercase and any other value, so callers must use these exact uppercase values. Also returns the observed entity type and leaderboard type values, which the gateway does not validate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "faceit_leaderboard_statuses"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.1/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 behavioral burden and does reasonably well: it discloses the strict uppercase validation upstream and states that the entity-type and leaderboard-type values it also returns are NOT validated by the gateway. That is real, non-obvious context an agent could not get from structured fields. It stops short of describing response shape or ordering.

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 tool's purpose and the enumerated values, followed by the validation caveat. Wording is tight and every sentence adds something, though the phrasing 'closed leaderboard status enum' then 'leaderboard status enum' is slightly repetitive.

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?

With no output schema, the description must explain what comes back — and it enumerates the three status values explicitly, which is the primary payload. It is slightly incomplete in that the secondary 'observed entity type and leaderboard type values' are mentioned but never enumerated or explained, so an agent still lacks detail on part of the return value.

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?

The tool takes zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. The description's discussion of 'values' concerns return payload, not inputs, so no parameter meaning is missing.

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 first two sentences give a specific verb and resource: it returns the closed leaderboard status enum, then names the exact members (ONGOING, UPCOMING, FINISHED). This clearly separates it from the sibling leaderboard-fetching tools, which return leaderboard data rather than valid enum values.

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 conveys an implied usage rule — callers must pass these exact uppercase values, and the upstream rejects lowercase — which is helpful guidance for anyone about to call faceit_leaderboard with a status filter. However, it never explicitly says when to call this tool versus simply hardcoding a status, nor does it name the sibling tools whose parameters these values feed.

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