Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_match

Fetch a VLR.gg Valorant match by ID to get event, UTC start, status, format, scores, maps, pick/ban, player stats, head-to-head and recent results.

Instructions

VLR.gg Valorant match detail and player statistics. Returns one VLR.gg match: event and stage, exact UTC start time, status (final, live, upcoming), format such as Bo3, both teams with series score, the pick/ban note, and every map with picker, round scores split into attack, defend and overtime, duration and per-player lines (agents, rating, ACS, K/D/A, KAST, ADR, headshot percent, first kills and deaths). all_maps_players holds the aggregate across maps. Also returns the teams' head-to-head history and each team's recent results. Player fields are omitted when VLR has not published them yet. Use vlr-match-economy, vlr-match-performance and vlr-match-rounds for the economy, kill-matrix and round-by-round tabs.

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

A4.2/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 the status value space (final/live/upcoming), what each map block contains, that `all_maps_players` is an aggregate, that head-to-head and recent results are appended, and the important caveat that player fields are omitted when VLR has not published them. It does not mention error behavior for an unknown id or whether live matches are partially populated, 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.

Conciseness5/5

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

Identity and scope are front-loaded in the first clause, the return contents are packed into two dense but non-redundant sentences, and the sibling routing closes it out. No sentence repeats the name, title, or schema information.

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?

There is no output schema, so the description must convey the return shape and it does so exhaustively, including nested map and per-player structures plus the aggregate field. It falls slightly short of complete because behavior for a missing or invalid match id (error vs empty) is unaddressed.

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?

There is one parameter with 100% schema description coverage, so the schema already explains that `id` is a numeric VLR match id sourced from vlr-matches/vlr-results/vlr-event-matches. The description adds nothing about the parameter, so the baseline of 3 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?

The description names a specific verb and resource ('Returns one VLR.gg match') and then enumerates the exact contents: event/stage, UTC start time, status enum values, format, series score, per-map round splits and per-player stat lines. It also distinguishes itself from the three sibling sub-tab tools, so an agent can separate it from vlr_match_economy/performance/rounds without opening any 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?

The final sentence explicitly routes economy, kill-matrix and round-by-round needs to the three sibling tools, which is clear alternative guidance. It does not explicitly state the inverse condition ('use this one for the full match overview and aggregate player stats'), though that is strongly implied by 'Returns one VLR.gg match' and 'all_maps_players holds the aggregate'.

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