Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

bo3_tournament

Read-only

Returns one BO3.gg tournament by slug: name, status, tier, event type, prize pool, dates, description, series, host city, country and region, stages with format and dates, the prize distribution by place and the participating teams with placement and prize money. Provide slug from bo3_tournaments and optionally game. Use it for an event's structure; use bo3_match_history for its matches.

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": {
      "slug": "<slug>"
    },
    "name": "bo3_tournament"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoOptional game: cs2 (default), valorant, lol, dota2, r6siege or mlbb.
slugYesRequired tournament slug from bo3_tournaments, for example pgl-masters-bucharest-2026.

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

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

Annotations already cover safety (readOnlyHint) and open-world scope, and the description adds substantive context about what is returned and where the identifier originates, with no contradiction. It stops short of noting payload size or any rate/size considerations for a rich nested response.

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, then a field enumeration, then two short routing sentences. The middle field list is long but earns its place by signaling coverage; nothing is redundant or padded.

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?

With an output schema present the field enumeration is technically redundant, but the description still supplies the prerequisite (slug source) and sibling routing an agent needs to call it correctly. Minor gap: no mention of pagination/absence behavior or how to go deeper (e.g. map pool, MVPs) via siblings.

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% and both parameters already describe themselves (including the game enum list and an example slug). The description only restates that slug comes from bo3_tournaments and that game is optional, adding minimal meaning beyond the schema, so the 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 one BO3.gg tournament by slug') and enumerates the payload (status, tier, prize pool, stages, prize distribution, teams), so an agent knows exactly what it gets. It is clearly distinct from bo3_tournaments (list) and bo3_match_history (matches).

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 the slug must come from bo3_tournaments and names bo3_match_history as the alternative for matches, plus 'use it for an event's structure'. It does not address the closely overlapping siblings bo3_tournament_stages, bo3_tournament_squads or bo3_tournament_map_pool, even though stages and teams are also returned here.

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