Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_competition_matches

Read-only

Get FACEIT competition match list. Returns one page of a competition's match list for a competition id and type. The upstream requires both id and type and rejects a missing type; an unknown id is an empty list. The sampled anonymous response was empty and its non-empty item shape is unverified, so each match is passed through as raw upstream JSON rather than a guessed DTO.

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>",
      "type": "<type>"
    },
    "name": "faceit_competition_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired competition id; the upstream returns an empty list for an unknown id.
pageNoOptional non-negative page number; default 0.
sizeNoOptional page size, 1-100; default 20.
typeYesRequired competition type such as championship; the upstream rejects a missing type.
player_idNoOptional player UUID filter.

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

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

Adds genuine behavior beyond the readOnly/openWorld annotations: results are a single page, upstream rejects a missing type, an unknown id returns an empty list instead of failing, and each item is passed through as raw upstream JSON because the non-empty item shape is unverified. This last point is an unusually valuable warning about return-value reliability. It stops short of covering auth or rate-limit behavior, keeping it out of the top band.

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?

Four sentences, front-loaded with the action and scope, and each sentence carries distinct information (scope, prerequisites, error semantics, response caveat). The phrasing about the 'sampled anonymous response' is slightly ledger-like for a caller-facing description but not padding.

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?

An output schema exists, so return structure need not be explained, and the description nonetheless flags that items are raw passthrough JSON. Combined with the stated error semantics and single-page scope, an agent has everything needed to call this correctly and interpret an empty result.

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 all five parameters are already documented in the schema, including defaults for page/size and the player_id filter. The description only restates the id/type requirement and the empty-list behavior, adding no semantics the schema does not already carry. Baseline 3 applies.

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 competition match list', then narrows to 'one page of a competition's match list'. The FACEIT + competition qualifier separates it from the swarm of generic *_matches siblings, though no sibling is named as an explicit alternative.

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?

Implicitly defines the calling context through prerequisites (both id and type required; missing type is rejected) and the edge case that an unknown id yields an empty list rather than an error. It never says when to prefer this over another match-listing tool, and no exclusions are given.

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