Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_championship_bracket

Fetch one FACEIT championship group and round bracket, returning match pairings with each side's player ID and faction number.

Instructions

FACEIT championship group bracket by group and round. Returns one group and round of a championship bracket: group number, delimiter, status, total and the bracket match pairings with each side's player id and faction number. The group and round parameters are required by the upstream; start and end bound the returned match range. An unknown championship 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>",
      "group": "<group>",
      "round": "<round>"
    },
    "name": "faceit_championship_bracket"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesChampionship UUID from faceit-championship-search.
endNoOptional end offset.
groupYesGroup number.
roundYesRound number.
startNoOptional non-negative start offset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a good job: it describes the returned fields, the match pairing structure, the meaning of start/end, and that an unknown championship returns 404. It stops short of documenting authentication, rate limits, or pagination behavior beyond the offset range.

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 description is three focused sentences with the core resource and filters front-loaded. There is little waste, though the opening phrase slightly restates the tool name rather than adding new information.

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?

For a five-parameter read tool with no annotations and no output schema, the description is fairly complete: it covers the return shape, required filters, offset semantics, and the 404 case. Missing authentication and rate-limit context are minor gaps rather than blockers.

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 coverage is 100%, so the schema already documents all five parameters. The description adds useful meaning by saying group and round are required upstream and that start/end bound the returned match range, but it does not add format or edge-case detail beyond that.

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?

The description clearly states that this tool retrieves a FACEIT championship group bracket filtered by group and round. It identifies the resource and the two key dimensions, but does not explicitly distinguish itself from sibling tools such as faceit_championship or faceit_championship_participants.

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?

It explains that group and round are required by the upstream and that start/end bound the match range, which helps an agent call the tool correctly. However, it does not say when to choose this tool over related championship tools or describe any exclusions or prerequisites.

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