Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

bo3_team_prize_money

Read-only

Returns BO3.gg teams ranked by the prize money won in tournaments that ended inside a day range (default last six months) for one game, with paging up to 100 per page: prize money in USD, tournament wins, country, region and roster with each player's career prize money and six-month rating. Provide game and optional from/to days; use a wide window for all-time leaders. Use it to compare team earnings; use bo3_tournaments for the events themselves.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bo3_team_prize_money"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional last day, YYYY-MM-DD (UTC). Default: today.
fromNoOptional first day, YYYY-MM-DD (UTC). Default: six months before to.
gameNoOptional game: cs2 (default), valorant, lol, dota2, r6siege or mlbb.
limitNoOptional page size 1 to 100, default 20.
offsetNoOptional zero-based offset, default 0.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's added value is in behavioral scope: default six-month window, paging up to 100 per page, and the returned fields. It doesn't discuss rate limits or error behavior, but the key operational constraints are disclosed.

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 the core behavior (ranked teams by prize money, date range, paging) and then appends usage and the sibling alternative. It's dense and earns most of its text, though the list of return fields is slightly verbose given an output schema exists.

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?

For a read-only ranking tool with full schema coverage and an output schema, the description covers the core behavior, defaults, pagination, and the relevant sibling alternative, leaving no material gap an agent would need to fill before calling it.

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 description coverage is 100%, so the schema already defines from/to, game, limit, and offset. The description adds minor semantic guidance ('wide window for all-time leaders') but otherwise repeats the date-range concept, which is the baseline expectation when the schema does the heavy lifting.

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?

The description names a specific resource (BO3.gg teams ranked by prize money), the scope (tournaments ending in a date range, one game), and the output fields, so an agent can distinguish it from sibling tools like bo3_team_rankings or bo3_tournaments 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this tool to compare team earnings and redirects to bo3_tournaments for the events themselves, plus advises providing game and optional from/to days and using a wide window for all-time leaders—clear when-to-use and when-not guidance.

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