Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_tournaments_past

Read-only

Get FACEIT player past tournament history. Returns one page of a player's past tournament history. The upstream answered the sampled anonymous requests with an empty list and its non-empty item shape is unverified, so each item is passed through as raw upstream JSON rather than a guessed DTO. A nickname with no history is a valid empty result.

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": {
      "nickname": "<nickname>"
    },
    "name": "faceit_tournaments_past"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional page size, 1-100; default 20.
offsetNoOptional non-negative row offset.
nicknameYesRequired FACEIT nickname.

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.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses that results are paginated (one page at a time), that items are raw unverified upstream JSON rather than a normalized DTO, and that empty lists are legitimate. That is real behavioral context an agent needs to parse responses and avoid false-negative conclusions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Reasonably front-loaded with the purpose in the first sentence, but sentence two largely restates sentence one ('Returns one page of a player's past tournament history'), costing space without new information. The remaining sentences about raw JSON and valid empty results do earn their place.

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 return values need not be described, yet the description still explains the raw-JSON item caveat that the output schema likely does not convey. Combined with pagination and valid-empty-result notes, an agent has what it needs to call and interpret this tool.

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 is 3, but the description adds the 'one page' framing that gives limit/offset meaning in context and reinforces nickname semantics. It stops short of restating ranges or defaults, which is appropriate since the schema already carries them.

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?

States a specific verb and resource: 'Get FACEIT player past tournament history', with scope narrowed to a single player and past tournaments. It does not name or contrast any sibling (e.g. sofascore_player_tournaments or faceit_competition_matches), so an agent must infer the distinction from the platform and player-centric framing.

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

Usage Guidelines3/5

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

Usage is implied through the required nickname and the explicit note that an empty history is a valid result, which usefully discourages retries or error handling on empty pages. There is no explicit when-to-use/when-not-to-use guidance or pointer to an alternative tool for current or upcoming tournaments.

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