Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora.mcp
OverviewDiscussionsAdmin

vlr_stats

Read-only

Returns VLR.gg's filterable Valorant player statistics table, 100 rows per page: agents played, maps, rounds, rating, ACS, K:D, KAST, ADR, per-round rates, first-kill and clutch stats. Filters are comma-separated tier (vct,vcl,t3,gc,cg,off), region (americas,emea,pacific,china,intl), role, agent and map names, plus timespan (all,30d,60d,90d or a season year from 2020 up to the current year) or a custom from and to date range (YYYY-MM-DD, both required, instead of timespan), side (all,t,ct), min_rounds, min_rating, sort and dir. Invalid filter values are rejected locally. Use it for league-wide player rankings; use vlr_event_stats for one event's table or vlr_player for one player's agent breakdown.

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": "vlr_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional last day of a custom date range, YYYY-MM-DD (UTC); requires from and replaces timespan.
dirNoOptional sort direction: desc (default) or asc.
mapNoOptional comma-separated map names such as ascent,bind.
fromNoOptional first day of a custom date range, YYYY-MM-DD (UTC); requires to and replaces timespan.
pageNoOptional 1-based page; defaults to 1.
roleNoOptional comma-separated agent roles: controller, initiator, sentinel, duelist.
sideNoOptional side: all (default), t (attack) or ct (defend).
sortNoOptional sort column: rating (default), maps, rnd, acs, kd, kast, adr, kpr, apr, fkfd, fkpr, fdpr, hsp, clp, cl, kmax, k, d, a, fk, fd.
tierNoOptional comma-separated tiers: vct, vcl, t3, gc, cg, off. Defaults to the site default (vct).
agentNoOptional comma-separated agents such as jett,sage.
regionNoOptional comma-separated regions: americas, emea, pacific, china, intl.
timespanNoOptional timespan: all, 30d, 60d (default), 90d or a four-digit year from 2020 up to the current year.
min_ratingNoOptional minimum player rating: 0 (all), 1300, 1400, 1500, 1550, 1650, 1750 or 1850.
min_roundsNoOptional minimum rounds played; site default 100.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / timespan / description
      Previous value: -"Optional timespan: all, 30d, 60d (default), 90d or a year 2020 to 2026."New value: +"Optional timespan: all, 30d, 60d (default), 90d or a four-digit year from 2020 up to the current year."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavior: 100 rows per page pagination and the fact that invalid filter values are rejected locally. It doesn't mention rate limits, 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?

Front-loaded with the resource and columns, then filters, then routing guidance. Dense but well-organized; the long filter enumeration is somewhat redundant with the schema but still readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists so return values needn't be explained, and annotations carry the safety profile. For a 14-param zero-required filter tool, the description gives enough to call it correctly and route to the right sibling.

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. The description restates enum values that already live in the schema (tiers, regions, timespan, sort, dir) and adds only the from/to-replaces-timespan interaction, which the schema also documents.

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 (Returns) and resource (VLR.gg's filterable Valorant player statistics table) and enumerates the columns produced. It explicitly differentiates itself from vlr_event_stats and vlr_player, so an agent can tell which stats tool to open.

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

Usage Guidelines5/5

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

The final sentence gives explicit when-to-use ('league-wide player rankings') and names both alternatives with their distinct scopes. No ambiguity about which sibling handles event-level or per-player data.

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

All Crawlora MCP toolsInspect
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