Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_event_agents

Retrieves VLR.gg event agent pick rates by map and overall, including games count, attack/defense round win rates, and team compositions to analyze event meta.

Instructions

VLR.gg Valorant event agent pick rates by map. Returns the agent pick-rate matrix of one VLR.gg event: for the whole event and for each map, the number of games, the attack-side and defense-side round win rates and the share of games in which each agent was played. Also returns, per map, each team's agents used and the agents picked in each of its matches (compositions). Use it to see an event's meta; vlr-stats gives per-player agent usage.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric VLR event id from vlr-events

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?

No annotations exist, so the description carries the whole burden, and it does well by disclosing the full shape of the payload rather than just naming it. It omits operational traits such as error behavior for an invalid event id, data freshness, or response size for large events, which for a read-only scraper-backed tool is a minor but real gap.

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 purpose is front-loaded in the first sentence, followed by a structured enumeration of return contents and a closing routing hint. The long middle sentence listing returned fields is justified because no output schema exists, though it reads as a run-on list.

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?

With no output schema and no annotations, the description fully compensates: it describes both the aggregate matrix and the per-map composition payload, plus the sibling alternative. An agent has everything needed to decide to call it and to interpret the result.

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 coverage is 100% and the single parameter's own description already says it is a 'Numeric VLR event id from vlr-events'. The prose adds no further meaning about the id's format or where to obtain it beyond what the schema states, so the baseline 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 the specific resource (VLR.gg event agent pick rates by map) and enumerates exactly what is returned: the pick-rate matrix, game counts, attack/defense round win rates, agent play share, and per-map team compositions. It is clearly distinguishable from the sibling aggregate tools like vlr_event_stats and vlr_stats.

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?

"Use it to see an event's meta; vlr-stats gives per-player agent usage" explicitly names an alternative and the condition that selects it. It gives no other exclusions (e.g. how this differs from vlr_event_stats, which sounds closely related), so it stops short of a full when/when-not statement.

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