Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_team

Retrieve a public FACEIT team profile by ID, including name, game, leader, members, social links, and status, to verify team details from bracket faction IDs.

Instructions

FACEIT team profile by id. Returns one public FACEIT team profile: name and nickname, game, leader, team type and status, description, country, avatar and cover, creation/update timestamps, social links, member and pending-member ids, and public member rows (guid, nickname, avatar, country and game list). Team ids are discovered from premade championship bracket faction ids in faceit-championship-bracket. An unknown id answers 404 and is returned as NotFound.

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_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTeam UUID from a premade bracket faction id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.4/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 burden and does so well: it establishes that the result is a single public profile, enumerates exactly what is exposed (including public member rows with guids and nicknames), and discloses the failure behavior ('An unknown id answers 404 and is returned as NotFound'). It does not mention auth requirements, rate limits, or whether private teams are excluded from lookup.

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?

Purpose and return scope are front-loaded, and the id-discovery and 404 notes follow in a logical order with no filler. The long enumeration of returned fields is dense but justified given the absence of an output schema; it is slightly over-packed into one run-on sentence.

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?

For a single-parameter read tool with no annotations and no output schema, the description supplies everything needed: what the resource is, the field set returned, how to obtain the id, and the error outcome. 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. The description earns an extra point by explaining where the 'id' value comes from — a premade championship bracket faction id — which is provenance information the schema field text only summarises as 'Team UUID from a premade bracket faction id.'

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?

Opens with a specific verb and resource: 'FACEIT team profile by id. Returns one public FACEIT team profile.' The scope ('one', 'public', 'team' as opposed to player/hub/championship resources in the sibling set) is unambiguous, so an agent can distinguish it from faceit_player without opening the 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?

Gives a concrete prerequisite for invocation: 'Team ids are discovered from premade championship bracket faction ids in faceit-championship-bracket,' which routes the agent to the right sibling for id discovery. It does not state when the tool should not be used or name an alternative for team lookups by name, so it falls short of full when/when-not guidance.

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