Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_tournaments

Find BO3.gg esports tournaments for a selected game by filtering status, tier, event type, and sort order, with paging to browse complete results.

Instructions

BO3.gg tournament list with filters. 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 prize pool first), up to 100 per page. Each tournament has its slug, name, status, tier, event type, prize pool in USD, dates and image; total and has_more page through the full list (over 3,000 CS2 events).

Input Schema

NameRequiredDescriptionDefault
gameNoGame; one of cs2, valorant, lol, dota2, r6siege, mlbb; defaults to cs2
sortNoOrder; one of newest, oldest, prize; defaults to newest
tierNoTournament tier; one of s, a, b, c, d
limitNoPage size, 1 to 100; defaults to 20
offsetNoZero-based offset; defaults to 0
statusNoTournament status; one of current, upcoming, finished, canceled, postponed
event_typeNoEvent type; one of lan, online

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does a good job disclosing return fields, page size up to 100, pagination via `total` and `has_more`, and dataset scale of over 3,000 CS2 events. It does not explicitly state read-only safety or rate limits, but 'Returns' and 'list' strongly imply a non-mutating read operation.

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 description is front-loaded with purpose and then efficiently packs filters, return fields, and pagination into a compact paragraph. It is dense but not padded; minor repetition of 'BO3.gg' is the only small inefficiency.

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 7-parameter list tool with no output schema and no annotations, the description is nearly complete: it covers filters, sort semantics, pagination, result fields, and dataset size. It leaves only minor gaps around explicit read-only assurance and when to choose this over the detail-oriented `bo3_tournament` sibling.

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 useful semantics beyond the schema: it explains that `sort=prize` means largest prize pool first, that pages hold up to 100 tournaments, and what fields each tournament includes. It does not add much for `game`, `limit`, or `offset`, which the schema already documents.

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: it returns a filtered list of BO3.gg esports tournaments for one game. The word 'list' and mention of paging distinguish it from the singular `bo3_tournament` detail sibling, though it does not explicitly name that alternative or articulate the distinction.

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 'tournament list with filters' and the list of filter enums, so an agent can infer this is for browsing or filtering tournaments. However, there is no explicit guidance on when to use this versus `bo3_tournament` or another sibling, and no stated 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