Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_hub_memberships

Read-only

Get FACEIT user hub memberships. Returns one page of a user's hub and competition memberships: membership id, user identity, the competition/hub reference (game, category, skill band, join permissions, player count, child ids), role names, highest role ranking and join date. This is the only anonymous hub-discovery path the FACEIT website exposes, so hub ids for faceit-hub come from here. category is a closed enum.

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": {
      "user_id": "<user_id>"
    },
    "name": "faceit_hub_memberships"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional page size, 1-50.
offsetNoOptional non-negative row offset.
user_idYesRequired FACEIT user UUID.
categoryNoOptional hub category from faceit-hub-categories: community, chat or ihl.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context of its own: results are paginated ("one page"), the call is anonymous, and the returned field set is summarized. It does not mention rate limits or ordering of pages, so it is solid but not rich.

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?

Three sentences with the identity of the tool and its unique routing value front-loaded. The middle sentence enumerating return fields is long and partly duplicates the output schema, but nothing 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?

An output schema exists, so the field enumeration is not strictly needed, but the description still contributes the pieces the schema cannot: pagination behavior, anonymous access, and where hub ids originate. An agent has enough to call it correctly, with only ordering/paging edge cases unaddressed.

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 limit, offset, user_id and category are already documented in the schema. The description mostly restates them, adding only that category is a closed enum and implying offset/limit are page controls; that is marginal value beyond the schema, so the baseline of 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 ("Get FACEIT user hub memberships") and immediately scopes the payload to one page of hub/competition memberships with named fields. It also carves out a unique role versus siblings by noting this is the only anonymous hub-discovery path, so an agent can see why it would pick this over faceit_hub or faceit_hubs.

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 routing rule: hub ids for faceit-hub come from here, and category values come from faceit-hub-categories. That is real when-to-use guidance tied to named siblings, but there is no explicit statement of when not to use it or what to do instead for non-hub lookups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources