Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

vlr_events

Read-only

Returns Valorant events from VLR.gg (ongoing, upcoming, completed) with id, status, prize pool, dates and region flag. Filter with tier (all, vct, vcl, t3, gc, cg, off) and region (all, americas, emea, pacific, china); page walks through completed events. Use vlr_event or vlr_event_matches with a returned id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
pageNoOptional 1-based page of completed events; defaults to 1.
tierNoOptional tier filter: all (default), vct, vcl, t3, gc, cg or off.
regionNoOptional region filter: all (default), americas, emea, pacific or china.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavior beyond that: which statuses are included, what fields come back, and the fact that pagination applies only to completed events. No rate limits or failure modes mentioned, but the bar is lower with annotations present.

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?

Two compact sentences; the return payload is front-loaded, filtering semantics come second, and the handoff to detail tools closes it out. Nothing is wasted and there is no 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?

An output schema exists, so enumerating returned fields is slightly redundant, but the description still covers filtering, pagination scope, and next-step routing adequately. An agent has everything needed to call it correctly.

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 all three parameters and their allowed values are already documented in the schema. The description restates the tier and region enum values without adding format or edge-case guidance. Baseline 3 is appropriate when the schema does the heavy lifting.

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), the statuses covered (ongoing, upcoming, completed), and the exact fields returned. It is clearly distinguishable from siblings vlr_event and vlr_event_matches, which it names.

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?

Explicitly routes the agent: 'Use vlr_event or vlr_event_matches with a returned id,' which is a concrete follow-up condition. It also explains that page only applies to completed events. It does not contrast with other event-adjacent siblings (vlr_matches, vlr_results), so guidance is strong but not exhaustive.

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

All Crawlora MCP toolsInspect
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.

Resources