Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_championship

Fetch full FACEIT championship details by UUID, including status, region, participant counts, schedule, and match settings. Use IDs found via championship search.

Instructions

FACEIT championship detail by id. Returns one FACEIT championship: identity and organizer, status and type, region, slots and participant counts, subscription/check-in/start timestamps (epoch milliseconds), entry checks, substitution policy, normalized match settings, schedule and groups, the organizer's FFA leaderboard points and role names. Championship ids are discovered through faceit-championship-search. An unknown id answers 404.

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": {
      "id": "<id>"
    },
    "name": "faceit_championship"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesChampionship UUID from faceit-championship-search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it declares the 404 behavior for an unknown id, specifies that timestamps are epoch milliseconds, and lists the substantive data sub-structures (substitution policy, normalized match settings, schedule/groups). It omits auth requirements and rate limits, which is the main remaining gap.

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?

The purpose and return-value inventory are front-loaded in the first two sentences, and the caveat about the id source and the 404 are placed at the end where they belong. The middle enumeration is dense but every item conveys real payload content, with no filler sentences.

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?

There is no output schema, so the description must describe the return value — and it does so exhaustively, down to the units of the timestamp fields and the nested organizational data. Combined with the id-discovery route and the 404 outcome, an agent has everything needed to call this correctly.

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?

There is a single parameter with 100% schema description coverage, and the schema already states it is a championship UUID sourced from faceit-championship-search. The description's statement that ids come from that sibling essentially restates the schema, adding no new syntax or format detail; the high-coverage baseline of 3 is appropriate.

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 ("FACEIT championship detail by id") and then enumerates exactly what the single returned object contains: identity, organizer, status, region, slots, timestamps, entry checks, schedule, groups, and FFA leaderboard points. That field inventory distinguishes it from faceit-championship-search (discovery), championship_bracket, and championship_participants without the agent needing to open any 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 precondition clearly: ids are discovered through faceit-championship-search, so the agent knows the retrieval must be preceded by a search call. It does not explicitly exclude the sibling detail tools (bracket, participants) or say when to prefer this over them, so it falls short of a full when/when-not statement.

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