Crawlora MCP

vlr_event_matches

Read-only

Returns every match of one VLR.gg Valorant event (optionally one stage via series_id taken from the returned stages list, or only completed or upcoming via group) (upcoming, live and completed) with teams, scores, stage and whether stats or VODs exist. Provide the numeric event id from vlr_events; use vlr_match with a returned id for map and player detail.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "vlr_event_matches"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Required numeric VLR event id from vlr_events.
`group`	No	Optional match group: completed or upcoming; omit it for both.
`series_id`	No	Optional stage id from the stages list of an earlier response (for example a week or a bracket round); omit it for every stage.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

addedInput schema / properties / group

Added value: +{
+  "description": "Optional match group: completed or upcoming; omit it for both.",
+  "type": "string"
+}

addedInput schema / properties / series_id

Added value: +{
+  "description": "Optional stage id from the stages list of an earlier response (for example a week or a bracket round); omit it for every stage.",
+  "type": "string"
+}

AddedOct 28, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already cover safety (readOnlyHint) and scope (openWorldHint). The description adds useful domain context about what comes back per match (teams, scores, stage, whether stats or VODs exist), but says nothing about result volume, pagination, or ordering for a potentially large event.

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?

Two sentences, front-loaded with the core behavior and ending with the routing hint. The nested parentheticals make the first sentence denser than ideal, but nothing is redundant.

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?

With an output schema, full parameter descriptions, and read-only annotations in place, the description covers purpose, input provenance, and next-step routing. Only list-size/ordering behavior for large events is left 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?

Schema description coverage is 100%, so all three parameters are already documented. The description adds only modest value, clarifying that series_id is a stage id drawn from a previously returned stages list and that group narrows to completed or upcoming; it also mentions 'live' results while the group parameter offers no live option, which slightly muddies the semantics.

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?

States a specific verb and resource ('Returns every match of one VLR.gg Valorant event') plus the scope filters (stage, group) and payload fields (teams, scores, stage, stats/VOD presence). It is clearly distinguishable from vlr_match, which the description names as the detail-level tool.

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?

Gives explicit prerequisites ('Provide the numeric event id from vlr_events') and an explicit hand-off rule ('use vlr_match with a returned id for map and player detail'). It also explains when to omit series_id or group. It stops short of stating when this tool should not be used at all (e.g. cross-event or team-scoped listing).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.