Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_player_leaderboard

Fetch CS2 player leaderboard data from BO3.gg for a date range, ranked by rating, K/D, kills, damage, assists, headshots, games, or rounds, with tier filters and paging.

Instructions

BO3.gg CS2 player leaderboard. Returns BO3.gg's CS2 player leaderboard over a day range (default: the last six months): players ranked by sort (rating, kd, kills, damage, assists, headshots, games, rounds) in order (desc, asc), optionally limited to games at one tournament tier (s to d), with paging. Each player has team, games, rounds and every per-game average as a stats map; players below the API's minimum-games threshold for the window are excluded (min_games_count). CS2 only.

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD (UTC); defaults to today
fromNoFirst day, YYYY-MM-DD (UTC); defaults to six months before to
sortNoStat to rank by; one of rating, kd, kills, damage, assists, headshots, games, rounds; defaults to rating
tierNoTournament tier of the games counted; one of s, a, b, c, d
limitNoPage size, 1 to 100; defaults to 20
orderNoDirection; one of desc, asc; defaults to desc
offsetNoZero-based offset; defaults to 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it states the default six-month window, the minimum-games exclusion, the returned per-player fields, and that paging is supported. It does not mention auth, rate limits, or pagination metadata, but for a public read-only leaderboard the behavioral picture is largely transparent.

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 a single dense paragraph but is front-loaded with the core purpose and organized from ranking controls to return shape. It is appropriately sized for a seven-parameter leaderboard with no output schema, though it could be split for readability.

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 usefully explains that each player includes team, games, rounds, and per-game averages in a stats map, and it notes the minimum-games exclusion. It omits return-level metadata such as total count or pagination envelope, but gives enough for an agent to invoke and interpret the tool 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 description coverage is 100%, so all seven parameters are already documented individually. The description mostly restates those fields and adds only modest context, such as the six-month default and the meaning of tier filtering; it also references `min_games_count` without a corresponding schema parameter, which is slightly confusing.

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 opens with a specific verb and resource ('Returns BO3.gg's CS2 player leaderboard') and states the ranking scope, date range, and CS2-only restriction. It clearly distinguishes this tool from a general player lookup or the sibling Valorant leaderboard without needing to open the 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?

It gives clear context for when to use it: retrieving ranked CS2 players over a day range, with controls for sort, order, tier, and paging. It does not explicitly name alternatives such as bo3_player_stats or bo3_player_recent_matches, so the agent must infer that this is the list/ranking tool rather than an individual-player tool.

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