Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_hubs

Fetches FACEIT hub summaries for up to 20 hub IDs, returning game, region, name, organizer, player count, category, and publication state.

Instructions

FACEIT hubs by id. Returns summary rows for up to 20 hub ids supplied as a repeated ids parameter: hub id, game and region, name, organizer, avatar, player count, category, publication state, relationship type, child ids and organizer tier. An unknown id is simply omitted from the item list. Hub ids come from faceit-hub-memberships.

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": {
      "ids": "<ids>"
    },
    "name": "faceit_hubs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesHub UUIDs; repeat the parameter for up to 20 hubs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/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 burden, and it does substantial work: it enumerates the returned fields, states the batch limit, and discloses that unknown ids are silently omitted rather than raising an error. It omits ordering guarantees and any permission or rate-limit considerations, but the core behavioral profile is present.

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 constraints are front-loaded, and the returned-field enumeration earns its space because no output schema exists. The field list is dense but not padded; no sentence is filler.

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 one-parameter lookup with no output schema and no annotations, the description supplies both the return shape and the edge-case behavior, which is what an agent needs. Minor gaps remain around result ordering and whether the game/region values are objects or strings.

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% and the single parameter is already documented as an array of hub UUIDs repeated up to 20 times. The description restates the repeated-parameter and 20-hub constraint, adding marginal value rather than new meaning. Baseline 3 is appropriate.

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 opens with a specific verb-and-resource statement ("FACEIT hubs by id") and immediately specifies the batch shape (summary rows for up to 20 ids). The word "summary" implicitly contrasts with the more detailed sibling faceit_hubs_detailed, but that sibling is never named, so the differentiation is inferred rather than stated.

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 gives clear context for when the tool applies and, importantly, routes the agent to faceit-hub-memberships as the source of valid hub ids. It also states the 20-id ceiling. There is no explicit when-not guidance or named alternative for retrieving a single hub versus many.

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