Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_tournament_map_pool

Retrieve a CS2 tournament's map pool by slug, including games and rounds per map, CT/T-side round wins and win percentage, plus pick and ban counts.

Instructions

BO3.gg CS2 tournament map pool. Returns the maps played at a CS2 tournament: games and rounds per map, CT-side and T-side round wins with the CT win percentage, and picked and banned counts. The upstream returns the whole event and ignores stage filters.

Input Schema

NameRequiredDescriptionDefault
slugYesCS2 tournament slug from bo3-tournaments, for example pgl-masters-bucharest-2026

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full disclosure burden and does useful work: it lists the returned metrics and warns that stage-level filtering is not honored upstream, which prevents an agent from expecting per-stage breakdowns. It stops short of covering error behavior for invalid slugs or pagination.

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?

Three sentences, front-loaded with the identity of the resource and followed by return contents, then the caveat. Dense and waste-free, though the leading fragment is a little clipped.

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?

There is no output schema, so the description must describe return values — and it does so concretely. Combined with a fully documented single parameter, an agent has enough to call it correctly; only edge-case behavior (unknown slug, empty pool) is unaddressed.

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?

The single slug parameter is already documented at 100% coverage in the schema, including its source (bo3-tournaments) and an example value. The description adds no additional meaning about slug format or lookup behavior, so 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 the specific resource (a CS2 tournament's map pool) and even enumerates what the payload contains (games/rounds per map, CT vs T round wins, CT win %, pick/ban counts). It is clearly distinct from sibling tools like bo3_tournament_stages or bo3_match_games, though it never names an alternative explicitly.

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?

The note that the upstream returns the whole event and ignores stage filters is an implicit us- age constraint, but it is stated as a data caveat rather than as guidance on when to call this versus bo3_tournament_stages or bo3_tournament. No explicit when/when-not framing.

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