Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_tournament

Fetch a BO3.gg tournament by slug to return its status, tier, prize pool, dates, stages, prize distribution, and participating teams with placements.

Instructions

BO3.gg tournament detail. Returns one BO3.gg tournament by slug: name, status, tier, event type, prize pool, dates, description, series, host city, country and region, its stages (format, status, dates), the prize distribution by place and the participating teams with their placement and prize money. The slug comes from bo3-tournaments.

Input Schema

NameRequiredDescriptionDefault
gameNoGame; one of cs2, valorant, lol, dota2, r6siege, mlbb; defaults to cs2
slugYesTournament slug from bo3-tournaments, for example pgl-masters-bucharest-2026

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations and no output schema, the description does real work by enumerating the returned payload (stages, prize distribution, participating teams with placement and prize money), which signals both read-only nature and response shape. However it says nothing about failure behavior for an unknown slug, rate limits, or whether the game parameter changes the underlying dataset.

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 identity sentence, then a single enumeration of the returned shape, then a provenance pointer. The middle sentence is long but every clause names a distinct field group rather than padding.

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?

Because there is no output schema, the description must carry the return contract, and it does so comprehensively (identity fields, stages, prize distribution, teams). Minor gaps remain around the game parameter's effect and error handling, but an agent has what it needs to call it correctly.

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%: both slug and game already carry descriptions, examples, and an enum with a documented default. The description adds only the provenance relation ('the slug comes from bo3-tournaments'), so the baseline 3 is appropriate.

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?

Opens with a specific verb+resource ('BO3.gg tournament detail. Returns one BO3.gg tournament by slug') and immediately enumerates the fields returned. The closing line routes the agent to bo3_tournaments for the slug, which cleanly separates this detail endpoint from its list sibling.

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?

The line 'The slug comes from bo3-tournaments' tells the agent the prerequisite lookup and implicitly when this tool applies (once you have a slug). It does not explicitly state when-not to use it or mention the sibling detail tools (bo3_tournament_stages, bo3_tournament_squads, bo3_tournament_mvps) that overlap this data.

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