Crawlora MCP

vlr_event_stats

Read-only

Returns the player statistics table of one VLR.gg Valorant event (filterable by side, role, agent, map, stage ids from vlr_event_matches, min_rounds, sort and dir): rating, ACS, K:D, KAST, ADR, per-round rates, first kills, clutches and totals for every player, optionally for one side (all, t, ct). Provide the numeric event id from vlr_events. For league-wide filtered stats use vlr_stats.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "vlr_event_stats"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Required numeric VLR event id from vlr_events.
`dir`	No	Optional sort direction: desc (default) or asc.
`map`	No	Optional comma-separated map names such as ascent,bind.
`role`	No	Optional comma-separated agent roles: controller, initiator, sentinel, duelist.
`side`	No	Optional side: all (default), t (attack) or ct (defend).
`sort`	No	Optional sort column, the same set as vlr_stats: rating (default), maps, rnd, acs, kd, kast, adr, kpr, apr, fkfd, fkpr, fdpr, hsp, clp, cl, kmax, k, d, a, fk or fd.
`agent`	No	Optional comma-separated agents such as jett,sage.
`stage`	No	Optional comma-separated stage ids from the stages list of vlr_event_matches.
`min_rounds`	No	Optional minimum rounds played; site default 0 for events.

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.

Changed7 schema fields changedOct 28, 2026

addedInput schema / properties / agent

Added value: +{
+  "description": "Optional comma-separated agents such as jett,sage.",
+  "type": "string"
+}

addedInput schema / properties / dir

Added value: +{
+  "description": "Optional sort direction: desc (default) or asc.",
+  "type": "string"
+}

addedInput schema / properties / map

Added value: +{
+  "description": "Optional comma-separated map names such as ascent,bind.",
+  "type": "string"
+}

addedInput schema / properties / min_rounds

Added value: +{
+  "description": "Optional minimum rounds played; site default 0 for events.",
+  "type": "integer"
+}

addedInput schema / properties / role

Added value: +{
+  "description": "Optional comma-separated agent roles: controller, initiator, sentinel, duelist.",
+  "type": "string"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "Optional sort column, the same set as vlr_stats: rating (default), maps, rnd, acs, kd, kast, adr, kpr, apr, fkfd, fkpr, fdpr, hsp, clp, cl, kmax, k, d, a, fk or fd.",
+  "type": "string"
+}

addedInput schema / properties / stage

Added value: +{
+  "description": "Optional comma-separated stage ids from the stages list of vlr_event_matches.",
+  "type": "string"
+}

AddedOct 28, 2026

TDQS

A4.4/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, so the safety profile is covered; the description adds what the response contains (full metric list and per-player granularity) and the scope constraint (single event, optional side filter). It omits return-shape details and pagination, which is acceptable given an output schema exists, but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with 'Returns the player statistics table' and the filters scoped in a single parenthetical; the two closing sentences add sourcing and the sibling routing with no filler. Dense but every clause earns its place.

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 an output schema present, the description need not explain return values, and it still covers required parameter provenance (event id from vlr_events) and the sibling alternative. It doesn't spell out pagination or sorting default behavior beyond the schema, a minor gap for a 9-parameter tool.

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 id, side, role, agent, map, stage, min_rounds, sort, and dir. The description restates the filter set and repeats the side values (all, t, ct) already listed in the schema, so it adds little syntax or format meaning beyond that.

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 and resource (returns the player statistics table for one VLR.gg Valorant event) and enumerates the metrics returned (rating, ACS, K:D, KAST, ADR, etc.). It also explicitly distinguishes itself from vlr_stats, so an agent can separate the two without opening either schema.

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 description gives concrete selection guidance: 'Provide the numeric event id from vlr_events' for this tool, and 'For league-wide filtered stats use vlr_stats.' That names the alternative and the condition that routes to it, which is exactly the when-to-use vs when-not-to-use information an agent needs.

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?