Crawlora MCP

bo3_tournaments

Read-only

Returns BO3.gg esports tournaments for one game with paging and filters: status (current, upcoming, finished, canceled, postponed), tier (s to d), event_type (lan, online) and sort (newest, oldest, prize for the largest pool first), up to 100 per page. Each has slug, name, status, tier, event type, prize pool in USD, dates and image; total and has_more page through the list. Use it to find events by tier or prize; use bo3_match_history for the matches themselves.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bo3_tournaments"
  }
}

Input Schema

Name	Required	Description
`game`	No	Optional game: cs2 (default), valorant, lol, dota2, r6siege or mlbb.
`sort`	No	Optional order: newest (default), oldest or prize (largest prize pool first).
`tier`	No	Optional tier: s, a, b, c or d.
`limit`	No	Optional page size 1 to 100, default 20.
`offset`	No	Optional zero-based offset, default 0.
`status`	No	Optional status: current, upcoming, finished, canceled or postponed.
`event_type`	No	Optional event type: lan or online.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare readOnly/openWorld, so the description carries the rest and does add real context: page cap of 100, total and has_more for paging through the full list, and the fields each record carries. It does not mention rate limits or auth, but for a read-only listing endpoint it is adequately transparent.

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 the core action and scope, then filters, then the routing sentence. Slightly dense and somewhat duplicative in listing record fields that the output schema already covers, but no sentence is wasted.

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?

With 7 optional params, annotations, and an output schema, the description covers scope, filtering dimensions, page-size ceiling, and the paging contract. Nothing an agent needs to call it correctly is missing.

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 every parameter is already documented, including the game list and enum values. The description restates the same filters and enum options without adding format, default, or interaction details beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource (returns BO3.gg esports tournaments) scoped to one game, and names the sibling it is not (bo3_match_history for matches). An agent can distinguish it from bo3_tournament or bo3_match_history without opening a schema.

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?

Explicitly says 'Use it to find events by tier or prize' and routes match-level needs to bo3_match_history. It gives a clear positive use case and one exclusion, but doesn't address when to prefer the single-tournament sibling bo3_tournament.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

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

Need Help?