Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_valorant_leaderboard

Retrieve BO3.gg Valorant player leaderboards for a date range, ranked by ACS, kills, deaths, damage, assists, or other stats with paging and minimum-games filtering.

Instructions

BO3.gg Valorant player leaderboard. Returns BO3.gg's Valorant player leaderboard over a day range (default: the last six months): players ranked by sort (acs, kills, deaths, damage, assists, first_kills, clutches, first_duels, games, rounds) in order (desc, asc) with paging. Each player has nickname, slug, games, rounds and every per-round average as a stats map; players below the API's minimum-games threshold for the window are excluded (min_games_count).

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 acs, kills, deaths, damage, assists, first_kills, clutches, first_duels, games, rounds; defaults to acs
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

A3.7/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 six-month window, default sort/order, paging, returned player fields, and the minimum-games exclusion. It does not cover auth, rate limits, or error behavior, which keeps it below a 5.

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 purpose is front-loaded in the first sentence, and the second sentence efficiently explains ranking, paging, return fields, and exclusion behavior. It is somewhat dense and repeats the full sort enum already present in the schema, but there is little wasted text.

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 six-parameter read tool with no output schema, the description is fairly complete: it explains filtering, sorting, paging, returned fields, and the minimum-games threshold. Remaining gaps are minor, such as whether the response includes total-count paging metadata and the unclear `min_games_count` reference.

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 documents all six parameters, including defaults and enum values. The description reinforces the day-range behavior and output shape, but adds little parameter-level meaning beyond the schema; it also references `min_games_count`, which is not an input parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: it returns BO3.gg's Valorant player leaderboard. It is specific about scope, sorting, and paging, but it does not distinguish this tool from the sibling `bo3_player_leaderboard`, which could create ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the explicit 'Valorant player leaderboard over a day range' scope, so an agent can infer when it applies. However, there is no explicit guidance about when to prefer this over `bo3_player_leaderboard` or other player-stat siblings.

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