Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_organizer

Retrieve a FACEIT organizer's public profile by ID, including name, type, plan limits, sponsors, social links, supported games, and region features.

Instructions

FACEIT organizer profile by id. Returns one organizer's public profile: name and type, plan-tier limits, publication state, avatar and cover, sponsors, public staff roles, social links, supported games, description, featuring countries, countries, geo regions and features. Organizer ids appear as organizer_id on championship and leaderboard rows. The staff account ids are deliberately not mirrored. An unknown id 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>"
    },
    "name": "faceit_organizer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrganizer UUID.

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, the description carries the full burden and does substantial work: it discloses the field set returned, states that staff account ids are deliberately omitted, and specifies that an unknown id answers 404. It does not explicitly state read-only semantics, auth requirements, or rate limits, leaving a modest gap for a no-annotation tool.

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?

Front-loaded with purpose, then return fields, then id provenance, then error behavior — a sensible progression with no filler. The one drawback is the long unpunctuated field enumeration, which reads as a run-on and could have been grouped more tightly.

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?

There is no output schema, so the description must describe returns, and it does so field-by-field. Combined with the id provenance and the 404 note, an agent has everything needed to call this single-parameter lookup correctly.

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% ('Organizer UUID.'), so the baseline is 3. The description goes beyond the schema by telling the agent where organizer ids can be harvested (organizer_id fields on championship and leaderboard rows), which is genuine added meaning for resolving the parameter.

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?

The description opens with a specific verb and resource: 'FACEIT organizer profile by id. Returns one organizer's public profile.' It immediately enumerates what a profile contains (name, type, plan-tier limits, sponsors, staff roles, social links, games, regions), which distinguishes it cleanly from siblings like faceit_championship or faceit_leaderboard that merely reference organizer_id.

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 explains where the required id comes from ('Organizer ids appear as organizer_id on championship and leaderboard rows'), which is real usage guidance for sourcing the parameter. It stops short of explicit when-not-to-use or naming a sibling alternative, so it lands just below the top band.

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