Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_team_prize_money

Rank BO3.gg teams by tournament prize money over a chosen date range for one game, with paging and roster earnings details.

Instructions

BO3.gg team prize money by period. Returns BO3.gg's teams ranked by the prize money they won in tournaments that ended inside a day range (default: the last six months), for one game with paging up to 100 per page. Each team has its prize money in USD, tournament wins, country and region and its current roster with each player's career prize money and six-month rating. total and has_more page through all teams that earned money in the window.

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD (UTC); defaults to today
fromNoFirst day, YYYY-MM-DD (UTC); defaults to six months before to
gameNoGame; one of cs2, valorant, lol, dota2, r6siege, mlbb; defaults to cs2
limitNoPage size, 1 to 100; defaults to 20
offsetNoZero-based offset; defaults to 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/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 well: it discloses the default window, the 100-per-page cap, and the exact per-team payload including roster with career prize money and six-month rating. It omits any mention of rate limits or which fields may be null, but the read-only listing nature is clear from context.

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?

Four sentences, front-loaded with the core purpose, then defaults, payload and paging. Slightly dense in the payload sentence but nothing 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 no output schema and no annotations, the description fully compensates: it explains the return shape (per-team money, wins, country/region, roster), paging metadata (total, has_more) and the default window, which is everything needed 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% with per-parameter descriptions and enum values, so the schema already documents from/to/game/limit/offset. The description restates the defaults and 100-per-page cap but adds no format or behavioral nuance beyond the schema.

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 concrete verb (rank teams) and resource (prize money won in tournaments ending within a day range) with clear scope: one game, paged up to 100. An agent can tell this apart from bo3_team_rankings or bo3_team_stats 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?

The description conveys the retrieval context well, including the default six-month window and per-game scoping. It never states when to prefer it over sibling team tools, so the guidance is clear but not comparative.

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