Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_match_rounds

Fetches a VLR.gg Valorant match's round-by-round replay by match ID, covering scores, winners, agents, economy, and kill/plant/defuse events; flags matches without available replay data.

Instructions

VLR.gg Valorant match round-by-round log. Returns the round log (the 2D replay data) of one VLR.gg match for every map that has one: for each round the score after it, the winner, the attacking team, every player's agent, credits left, spend, armor and weapon, and the ordered events (kills with weapon, spike plants and defuses) with their round clock. available is false when VLR has no replay for the match.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric VLR match id from vlr-matches, vlr-results or vlr-event-matches

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, the description carries the full burden and does well: it discloses that data is returned per map only when a replay exists, and that `available` is false when VLR has no replay. It does not cover error behavior or rate limits, but for a read-only retrieval tool the behavioral disclosure is solid.

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?

The first sentence identifies the source and resource immediately, then the description enumerates exactly what is returned per round and closes with the availability caveat. It is dense but front-loaded and every sentence contributes useful information.

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?

There is no output schema and no annotation coverage, so the description must explain the return values, which it does in detail: round score, winner, attacking team, player agents, economy, armor, weapons, and ordered events. It also explains the `available` flag, making the definition complete for a one-parameter fetch 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?

The single `id` parameter has 100% schema description coverage, including which sibling tools supply the numeric VLR match id. The main description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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?

The description states a specific verb and resource: it returns the round-by-round log (2D replay data) of one VLR.gg match. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as vlr_match, vlr_match_economy, or vlr_match_performance.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The detailed return description implies it is for round-level replay data, but an agent must infer that on its own.

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