Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_event_matches

Retrieve every match from a VLR.gg Valorant event, including upcoming, live, and completed games with teams, scores, stage, and stats or VOD availability; filter by match group or stage.

Instructions

VLR.gg Valorant event match list. Returns every match of one VLR.gg event (upcoming, live and completed) with teams, scores, stage and whether stats or VODs exist. Use vlr-match with a returned id for map detail.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric VLR event id from vlr-events
groupNoMatch group; one of completed, upcoming; omit for both
series_idNoStage id from the stages list of an earlier response (a week, group or bracket round); omit for every stage

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 burden and does it reasonably well: it discloses that all match states (upcoming, live, completed) are returned and enumerates the payload fields — teams, scores, stage, and stats/VOD availability flags. It omits pagination/volume behavior and error handling for an invalid id, which keeps it short of 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?

Three short sentences: what it returns, what's in the payload, and where to go next. The return-scope statement is front-loaded and nothing is repeated from the schema.

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 and no annotations, but the description compensates by naming the returned fields and states, which is what an agent needs to decide to call it. It could add id provenance (from vlr_events) to be fully self-contained.

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%, so the schema already documents `id`, the `group` enum and `series_id`. The description mentions the state coverage (upcoming/live/completed) but adds no syntax, combination rules, or default behavior for the optional filters, so 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 gives a specific verb and resource ('Returns every match of one VLR.gg event') and scopes it to a single event, which separates it from broader siblings like vlr_matches/vlr_results. It also names the follow-up sibling vlr_match for map-level detail, so an agent can distinguish the two without opening a 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?

It explicitly routes the agent forward: 'Use vlr-match with a returned `id` for map detail.' It does not, however, state when to prefer this over vlr_matches or vlr_results, nor that the required `id` must first come from vlr_events — that prerequisite lives only in the schema.

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