Crawlora MCP

bo3_player_leaderboard

Read-only

Returns BO3.gg's CS2 player leaderboard over a day range (default last six months): players ranked by sort (rating, kd, kills, damage, assists, headshots, games, rounds) in order (desc or 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 in a stats map; min_games_count is the window's minimum-games threshold. CS2 only. Use it to rank players; use bo3_player_stats for one player's totals.

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_player_leaderboard"
  }
}

Input Schema

Name	Required	Description
`to`	No	Optional last day, YYYY-MM-DD (UTC). Default: today.
`from`	No	Optional first day, YYYY-MM-DD (UTC). Default: six months before to.
`sort`	No	Optional stat to rank by: rating (default), kd, kills, damage, assists, headshots, games or rounds.
`tier`	No	Optional tournament tier of the games counted: s, a, b, c or d.
`limit`	No	Optional page size 1 to 100, default 20.
`order`	No	Optional direction: desc (default) or asc.
`offset`	No	Optional zero-based offset, default 0.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, and the description adds real context: the default six-month window, page-based retrieval, what each row contains (team, games, rounds, per-game averages in a stats map) and what min_games_count means. It does not state pagination ceilings or ordering stability, but the behavioral picture is solid.

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 constraints, then the routing sentence — a sensible order. It is a single dense paragraph, and the long enumeration of sort values partly duplicates the schema, but nothing is wasted.

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?

For a 7-parameter, all-optional paged read with an output schema present, the description covers defaults, filtering, paging and result shape, and names the alternative tool. Since an output schema exists, deeper return-value detail is unnecessary, so remaining gaps are minor.

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%, so the schema already documents every parameter with defaults and the tier enum. The description mostly restates those (sort values, order, tier s–d, default six months), adding only light framing; 'min_games_count' is a response field, not a parameter. 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 BO3.gg's CS2 player leaderboard') plus scope (day range, sorting, tier filter, paging). It explicitly separates itself from the sibling 'bo3_player_stats' and its 'CS2 only' note also distinguishes it from 'bo3_valorant_leaderboard'.

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 'Use it to rank players; use bo3_player_stats for one player's totals', naming the right alternative and the condition that selects it. It does not spell out when to omit the tier filter or when a leaderboard is the wrong tool, so it falls short of a full when/when-not statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

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

Need Help?