Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_match_performance

Retrieve VLR.gg Valorant match performance data with per-map and whole-match kill matrices plus advanced player stats for a match ID; check availability when VLR has not published the tab.

Instructions

VLR.gg Valorant match performance. Returns the Performance tab of one VLR.gg match for every map and for the whole match: player-versus-player kill matrices (overall kills and deaths, first kills and deaths, and Operator kills and deaths) and per-player advanced stats (2K to 5K multi-kills, 1v1 to 1v5 clutches, econ rating, spike plants and defuses). available is false while VLR has not published the tab.

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
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the content returned and the important `available` flag behavior when VLR has not published the tab, but it does not describe error behavior, empty-result handling, rate limits, or other operational traits beyond that availability note.

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?

The description is front-loaded with the core purpose and uses a compact enumeration of returned stats. It is slightly dense but every clause helps specify the Performance tab contents, and the availability caveat is placed cleanly at the end.

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?

Given the simple one-parameter schema, no output schema, and no annotations, the description is largely complete: it explains what the tool returns and when data may be unavailable. It could be stronger only by adding more explicit failure or alternative-selection guidance.

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 numeric VLR match id sourced from vlr-matches, vlr-results, or vlr-event-matches. The description adds little parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 the exact resource and scope: the Performance tab of one VLR.gg Valorant match, for every map and for the whole match. It then enumerates the specific data returned (kill matrices, multi-kills, clutches, econ rating, plants/defuses), which clearly distinguishes it from sibling match tools such as vlr_match_economy or vlr_match_rounds.

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

Usage Guidelines3/5

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

The description implies when the tool is useful by explaining that it returns the Performance tab, but it does not explicitly name alternatives or say when to use this versus vlr_match, vlr_match_economy, or other match tools. The `available` flag gives a useful availability condition, but selection guidance remains implicit.

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