Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_event_stats

Get per-player Valorant statistics for a single VLR.gg event, including rating, ACS, K:D, KAST and ADR, filtered by side, map, agent, role or stage.

Instructions

VLR.gg Valorant event player statistics. Returns the player statistics table of one VLR.gg event (rating, ACS, K:D, KAST, ADR, per-round rates, first kills, clutches, totals) for every player who appeared, optionally for one side (all, t attack, ct defend). For league-wide filtered statistics use vlr-stats.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric VLR event id from vlr-events
dirNoSort direction; one of desc, asc; defaults to desc
mapNoComma-separated map names, for example ascent,bind; the same 13 maps as vlr-stats
roleNoComma-separated agent roles; any of controller, initiator, sentinel, duelist
sideNoSide; one of all, t, ct; defaults to all
sortNoSort column, the same set as vlr-stats; defaults to rating
agentNoComma-separated agents, for example jett,sage; the same 29 agents as vlr-stats
stageNoComma-separated stage ids from the stages list of vlr-event-matches
min_roundsNoMinimum rounds played; 0 to 100000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It does disclose the return shape ('table ... for every player who appeared') and that side filtering is optional, but says nothing about pagination, size of the result, whether stats are per-map or aggregate, or any rate/permission constraints.

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?

Two sentences, front-loaded with the resource and back-loaded with the routing rule. The long metric parenthetical is dense but earns its place given there is no output schema; it is the longest element yet still functional.

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?

With 9 parameters, no output schema, and no annotations, the description does the important work: it names the returned fields and states the population (every player who appeared, optionally one side). Filter semantics are delegated entirely to a fully-covered schema, which is acceptable; only result-size/aggregation behavior is left unknown.

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

Parameters4/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, but the description adds real meaning: it glosses the `side` enum as 't attack, ct defend', which the schema itself does not, and clarifies there is no per-player filter. It doesn't add semantics for sort/map/agent/role, which rely on their 'same as vlr-stats' schema notes.

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+resource ('Returns the player statistics table of one VLR.gg event') and enumerates the metrics returned. It explicitly distinguishes itself from the sibling vlr-stats, so an agent can route between the two without opening a 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?

Ends with an explicit routing rule: 'For league-wide filtered statistics use vlr-stats.' That gives one clear alternative with its selecting condition. It does not address other nearby siblings (vlr_event, vlr_event_matches, vlr_match_performance), so guidance is clear but not exhaustive.

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