Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_matches

Retrieve upcoming and live Valorant matches from VLR.gg grouped by day, with teams, event, stage, ETA, status, and stats or VOD availability for schedule tracking.

Instructions

VLR.gg upcoming and live Valorant matches. Returns the Valorant match schedule from VLR.gg: upcoming and live matches grouped by day with both teams, country flags, event, stage, ETA and whether stats or VODs exist. status is upcoming, live or completed. time_label is the time shown on the site, whose timezone is not guaranteed; use vlr-match for an exact UTC start time. Use vlr-results for finished matches.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number; defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.4/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 well: it discloses returned fields, day grouping, status values, and a timezone caveat for `time_label`. It does not mention pagination behavior or result limits, and the stated `completed` status is slightly at odds with the advertised upcoming/live scope.

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 description is front-loaded, compact, and free of waste. The scope, returned fields, timezone caveat, and alternatives are all packed into a few sentences without repetition.

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 appropriately explains what is returned: matches grouped by day with teams, flags, event, stage, ETA, stats/VOD presence, and status. It is nearly complete, but omits pagination semantics for the `page` parameter and leaves the `completed` status ambiguity unresolved.

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%, so the single `page` parameter is already fully documented in the schema. The description adds no parameter-specific detail beyond what the schema provides, which is the expected baseline here.

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 states a specific resource and scope: VLR.gg upcoming and live Valorant matches, returned as a schedule grouped by day. It also distinguishes itself from `vlr-results` for finished matches and `vlr-match` for exact UTC start times, so an agent can tell what this tool is for without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit routing guidance: use `vlr-match` when an exact UTC start time is needed, and use `vlr-results` for finished matches. That makes the when-to-use-versus-sibling decision clear rather than leaving it to inference.

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