Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_events

Fetch Valorant events from VLR.gg—ongoing, upcoming, and completed—with prize pool, dates, region flags, and filters by tier or region; use returned IDs for event details.

Instructions

VLR.gg Valorant events. Returns Valorant events from VLR.gg: ongoing, upcoming and completed events with prize pool, dates and region flag. Filter by tier (all, vct, vcl, t3, gc, cg, off) and region (all, americas, emea, pacific, china); page pages through completed events. Use vlr-event with a returned id.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number; defaults to 1
tierNoEvent tier; one of all, vct, vcl, t3, gc, cg, off; defaults to all
regionNoEvent region; one of all, americas, emea, pacific, china; defaults to all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/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 mostly meets it: 'Returns' frames this as a read, and it enumerates the returned fields (prize pool, dates, region flag) despite there being no output schema. It omits any note on whether ongoing/upcoming events are confined to page 1 or how large a page is, which is relevant for a paginated list.

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?

Three dense sentences, front-loaded with what is returned before the filtering and follow-up details; no sentence is filler. The lead fragment 'VLR.gg Valorant events.' is slightly redundant with the sentence that follows but earns its place as a scannable header.

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?

For a three-param, zero-required list tool with no annotations and no output schema, the description covers source, returned fields, filters, pagination scope and the next-step tool — enough to call it correctly. It stops short of describing page size or ordering of ongoing vs upcoming events, which would fully close the loop.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description exceeds that by explaining that `page` applies specifically to completed events — a semantic the schema's generic '1-based page number' does not provide. The inline enum echoes add little since the schema already enumerates both filters.

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 Valorant events from VLR.gg) plus the exact payload contents: ongoing, upcoming and completed events with prize pool, dates and region flag. It also distinguishes itself from the sibling detail tool by saying 'Use vlr-event with a returned id', so an agent can tell listing from detail without opening either 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?

The handoff sentence 'Use vlr-event with a returned `id`' makes the list-then-detail workflow explicit, which is real routing guidance. It does not, however, cover the other plausible alternatives in the sibling set (vlr_matches, vlr_results, vlr_search) or state when this tool is the wrong choice.

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