Crawlora MCP

bo3_valorant_leaderboard

Read-only

Returns BO3.gg's Valorant player leaderboard over a day range (default last six months): players ranked by sort (acs, kills, deaths, damage, assists, first_kills, clutches, first_duels, games, rounds) in order (desc or asc) with paging, each with nickname, slug, games, rounds and every per-round average in a stats map; min_games_count is the window's threshold. Use it to rank Valorant players; for CS2 use bo3_player_leaderboard.

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_valorant_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: acs (default), kills, deaths, damage, assists, first_kills, clutches, first_duels, games or rounds.
`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/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. The description adds the default date range, sort options, ordering, paging behavior, and a summary of returned fields (nickname, slug, games, rounds, per-round averages). It does not mention rate limits or authentication, but for a read-only query endpoint the added context is substantial.

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 sentence front-loaded with the core purpose, followed by a short usage sentence. Every clause conveys useful information, though the long enumeration of sort options slightly increases cognitive load.

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?

An output schema exists, so the description need not fully document return values. It covers defaults, sorting, paging, and the CS2 alternative, making it complete enough for an agent to call correctly. The only blemish is the phantom min_games_count reference, which is not in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. However, the description mentions 'min_games_count is the window's threshold' even though the input schema has no such parameter (additionalProperties: false). This mismatch could mislead an agent into trying to pass a non-existent argument. The rest of the description aligns with the schema but adds little beyond it.

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 states a specific verb ('Returns') and resource ('BO3.gg's Valorant player leaderboard'), includes the scope (day range default six months), and explicitly distinguishes itself from the CS2 sibling (bo3_player_leaderboard). An agent can identify the tool's exact function without opening 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?

The description says 'Use it to rank Valorant players' and names the CS2 alternative explicitly. It provides clear context for when to use this tool, though it does not list exclusions beyond the CS2 case (e.g., when to prefer a team leaderboard).

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?