Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_best_clips

Read-only

Get FACEIT player best clips in a time window. Returns a player's best Allstar clips inside an inclusive time window: the same clip row shape as faceit-clips, ordered by the upstream best-clip ranking. Both from and to are required RFC3339 timestamps. Only cs2 has Allstar clips; a window with no clips is a valid empty list. The upstream ignores offset on this route, so no offset parameter is exposed.

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": {
      "game": "<game>",
      "user_id": "<user_id>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "faceit_best_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRequired inclusive upper bound as an RFC3339 timestamp.
fromYesRequired inclusive lower bound as an RFC3339 timestamp.
gameYesRequired game slug; only cs2 has Allstar clips.
limitNoOptional page size, 1-100; default 10.
user_idYesRequired FACEIT user UUID.

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description goes beyond them: it discloses result ordering, that an empty window is a valid empty list rather than an error, and that upstream ignores offset so no offset param exists. Auth requirements and rate-limit behavior are not mentioned.

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

Conciseness5/5

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

Front-loads the purpose, then layers ordering, timestamp requirement, game restriction, empty-result semantics, and the offset omission. Every sentence carries information and there is no 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 return shape needn't be explained, and the description still covers ordering, empty results, and game applicability. Minor gaps remain: no mention of how limit interacts with the time window or of pagination limits beyond the schema's 1-100.

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 the schema already documents every parameter including RFC3339 formats and the 1-100 limit range. The description reinforces that from/to are required and inclusive and explains the deliberate absence of offset, but adds little syntax or meaning beyond the schema.

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?

Names a specific verb+resource (player best clips) and immediately scopes it by time window. It distinguishes itself from faceit_clips by stating it returns the same row shape but ordered by the upstream best-clip ranking, so an agent can tell the two apart without inspecting schemas.

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 clear selection condition (retrieving best/all-star ranked clips within a window) and a hard applicability constraint (only cs2 has Allstar clips). It stops short of explicitly saying when to prefer faceit_clips or faceit_match_clips instead, leaving that inference to the caller.

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