Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

faceit_tournaments_past

Retrieve a player's past FACEIT tournament history by nickname with pagination via limit and offset, enabling review of prior tournament participation from raw upstream JSON.

Instructions

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.
nicknameYesFACEIT nickname.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description does substantial work: it discloses pagination behavior, warns that item shape is unverified and passed through as raw upstream JSON, and clarifies that an empty list is a valid result. It does not cover authentication needs or rate limits, but the behavioral disclosure is well above the bare minimum.

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 is front-loaded in the first sentence, followed by pagination and then the important caveat about raw upstream JSON. It is appropriately sized, though the explanation of the unverified item shape is slightly verbose for a simple lookup tool.

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 tool with no output schema and no annotations, the description explains the return shape (raw upstream JSON, one page) and the valid empty-result case. It leaves authentication and rate-limit behavior unstated, but the critical caveat about unverified item structure makes it largely complete for correct invocation.

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 description coverage is 100%, so the schema already explains nickname, limit, and offset. The description adds page-level context ('returns one page') and empty-result semantics, but does not add syntax or constraints beyond what the schema provides.

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 states a specific verb and resource: returning a FACEIT player's past tournament history, one page at a time. It is clearly distinguishable from sibling lookup tools like faceit_championship or faceit_hubs, though it does not explicitly name an alternative tool for contrast.

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 by the required nickname and paging parameters, and the note that 'a nickname with no history is a valid empty result' is helpful context. However, there is no explicit guidance on when to use this versus related tournament tools, nor any stated prerequisites or exclusions.

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