Crawlora MCP

vlr_match_rounds

Read-only

Returns the round log (2D replay data) of one VLR.gg Valorant match for every map that has one: per round the score after it, winner, attacking team, each player's agent, credits left, spend, armor and weapon, and the ordered kill, spike plant and defuse events with round clock and weapon. available is false when VLR has no replay. Provide the numeric match id from vlr_matches, vlr_results or vlr_event_matches; use vlr_match_economy for aggregate economy and vlr_match for the scoreboard.

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_match_rounds"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required numeric VLR match id from vlr_matches, vlr_results or an event page.

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.

AddedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds substantive behavior beyond them: the per-round field set returned, that coverage is per-map and only for maps that have a replay, and that `available` is false when VLR has no replay. It stops short of noting rate limits, pagination or payload size for what is described as 2D replay data.

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 payload, then the availability caveat, then the id source and alternatives—good ordering. The long middle enumeration of round fields is somewhat redundant given an output schema exists, but each clause is informative rather than filler.

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 single-parameter read tool with both annotations and an output schema, this covers what an agent needs: what comes back, per-map scoping, the empty-replay signal, and where to source the id. Nothing essential is missing.

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% and the single `id` parameter is already documented as a required numeric VLR match id. The description adds only slightly—naming vlr_matches/vlr_results/vlr_event_matches as the concrete sources for the id—so the baseline 3 for schema-covered params applies.

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?

Specific verb+resource ('Returns the round log (2D replay data) of one VLR.gg Valorant match'), with the exact payload enumerated (round score, winner, agent, credits, kill/plant/defuse events). It is immediately distinguishable from vlr_match (scoreboard) and vlr_match_economy (aggregate economy), which it names.

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?

Explicitly routes the agent: use vlr_match_economy for aggregate economy and vlr_match for the scoreboard, and it tells how to obtain the required id (from vlr_matches, vlr_results or vlr_event_matches). It also flags the no-replay case via `available is false`, so the agent knows what a partial/empty result means.

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.