Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_stats

Retrieve and filter VLR.gg Valorant player statistics by tier, region, role, agent, map, timespan, side, rounds, and rating, with sortable columns and pagination.

Instructions

VLR.gg Valorant player statistics with filters. Returns VLR.gg's player statistics table (100 rows per page): agents played, maps, rounds, rating, ACS, K:D, KAST, ADR, KPR, APR, first-kill and clutch rates and totals. Filter with comma-separated tier (vct, vcl, t3, gc, cg, off), region (americas, emea, pacific, china, intl), role (controller, initiator, sentinel, duelist), agent and map names, plus timespan (all, 30d, 60d, 90d or a season year from 2020 up to the current year), side (all, t, ct), min_rounds and min_rating; sort with sort and dir.

Input Schema

NameRequiredDescriptionDefault
toNoLast day of a custom date range, YYYY-MM-DD (UTC); requires from and replaces timespan
dirNoSort direction; one of asc, desc; defaults to desc
mapNoComma-separated maps from abyss, bind, corrode, haven, lotus, summit, sunset, ascent, breeze, fracture, icebox, pearl, split
fromNoFirst day of a custom date range, YYYY-MM-DD (UTC); requires to and replaces timespan
pageNo1-based page number; defaults to 1
roleNoComma-separated roles from controller, initiator, sentinel, duelist
sideNoSide; one of all, t, ct
sortNoSort column; one of rating, maps, rnd, acs, kd, kast, adr, kpr, apr, fkfd, fkpr, fdpr, hsp, clp, cl, kmax, k, d, a, fk, fd; defaults to rating
tierNoComma-separated tiers from vct, vcl, t3, gc, cg, off; site default vct
agentNoComma-separated agents from astra, brimstone, clove, harbor, miks, omen, viper, breach, fade, gekko, kayo, skye, sova, tejo, chamber, cypher, deadlock, killjoy, sage, veto, vyse, iso, jett, neon, phoenix, raze, reyna, waylay, yoru
regionNoComma-separated regions from americas, emea, pacific, china, intl
timespanNoTimespan; one of all, 30d, 60d, 90d or a four-digit season year from 2020 up to the current year (2020, 2021, 2022, 2023, 2024, 2025, 2026 today; a new year is accepted when it starts); site default 60d
min_ratingNoMinimum player rating; one of 0, 1300, 1400, 1500, 1550, 1650, 1750, 1850
min_roundsNoMinimum rounds played; site default 100

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 and no output schema, the description carries the burden and does real work: it discloses the payload (the full column list), the page size of 100 rows, and that filters are comma-separated multi-value. Gaps remain — no mention of total page count limits, caching freshness, or what happens when filters yield zero rows.

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 purpose and return shape, then filters, then sorting — a logical order in three dense sentences. It is somewhat verbose by re-listing enum values the schema already carries, but nothing is ambiguous or wasted at the sentence level.

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 14-parameter tool with no output schema and no annotations, the description supplies the return-field inventory and pagination contract that would otherwise be missing. The main shortfall is that two parameters (from/to) go undiscussed in the prose, deferring entirely to the schema.

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 baseline is 3, and the description largely restates what the schema already enumerates (tier, region, role, agent, map, timespan, side, sort, dir). It omits `from`/`to` custom date range entirely and never explains the non-obvious `min_rating` scale (0, 1300, 1400...) beyond the enum itself.

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?

States a specific resource and scope: VLR.gg's Valorant player statistics table, with the exact columns it aggregates (rating, ACS, KAST, ADR, first-kill and clutch rates). That distinguishes it in substance from the match/team/event siblings, though it never names an alternative tool (e.g. vlr_player or vlr_event_stats) to route between them.

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 rather than stated: the description tells the agent how to filter and sort but not when this aggregate leaderboard is the right choice versus a player profile, match, or event-stats tool. No exclusions, no prerequisite conditions, no guidance on defaults or empty-result scenarios.

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