Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_hubs_detailed

Fetch full FACEIT hub objects for up to 20 IDs in one bulk call, including identity, game, region, owner, player counts, settings, and permissions.

Instructions

FACEIT full hub objects for up to 20 ids. Returns full hub objects for up to 20 hub ids through the v2 bulk read: identity, description, game/region/category, organizer and owner, publication flags, slot and player counts, skill band, join permissions, rules id, images, checks, child ids, role identities, points and queue/application/chat settings. Unlike faceit-hubs (summaries) and faceit-hub (one id), this resolves several full hubs in one call. An unknown id is omitted from the item list.

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

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

A4.3/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 behavioral burden and does well: it discloses the 20-id bulk cap, the partial-success semantics for unknown ids, and enumerates the returned fields including publication flags, join permissions and queue/application/chat settings. It omits access requirements, rate limits, and whether the read is subject to visibility restrictions, which keeps it off a 5.

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 the sibling differentiation lead, and the alternative sentence closes the loop. The long middle sentence enumerating returned fields is dense but earns its place because there is no output schema; minor redundancy with the schema over the 20-item cap is the only waste.

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 bulk read with no annotations and no output schema, the description supplies exactly the missing pieces: return shape, cap, and error/omission behavior. Only auth and visibility preconditions are absent, which is a modest gap rather than a blocking one.

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 ids parameter is already documented as an array of hub UUIDs with the 20-item cap. The description restates the cap and adds the resolution semantics (unknown ids dropped from results), but adds little beyond the schema's own text; baseline 3 applies.

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?

States a specific verb and resource ("Returns full hub objects") and immediately bounds the scope ("up to 20 ids"). It explicitly contrasts itself with faceit-hubs (summaries) and faceit-hub (one id), so an agent can pick this tool without opening any sibling schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description names the two alternatives and the condition that selects this one: several full hubs in one call. It also adds an operational guideline for the failure case ("An unknown id is omitted from the item list"), which tells the agent how to interpret a short result set.

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