Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

vlr_matches

Read-only

Returns upcoming and live Valorant matches from VLR.gg grouped by day: both teams with country flags, event, stage, ETA and whether stats or VODs exist. status is upcoming, live or completed; time_label is the site's displayed time with an unspecified timezone, so use vlr_match for an exact UTC start. Optional page. Use vlr_results for finished matches.

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_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional 1-based page number; defaults to 1.

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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds useful behavioral detail: it describes the returned fields (teams with flags, event, stage, ETA, stats/VOD availability) and warns that time_label uses an unspecified timezone, directing to vlr_match for precise UTC.

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?

Front-loaded with the core purpose and efficiently covers alternatives and caveats in a few sentences. Minor redundancy from the 'upcoming and live' vs 'completed' phrasing slightly undermines structure but overall it is concise.

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?

Given the simple schema, annotations, and an output schema, the description is largely complete: it covers data returned, sibling routing, and timezone caveat. It doesn't mention pagination limits or behavior for empty pages, but those are minor for this tool.

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?

Only one optional parameter (page) with full schema coverage. The description merely notes 'Optional page', adding no meaning beyond the schema's existing description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Returns upcoming and live Valorant matches from VLR.gg grouped by day') and distinguishes itself from siblings like vlr_results and vlr_match. However, the first sentence says 'upcoming and live' while a later sentence says status can also be 'completed', creating slight internal ambiguity about scope.

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?

Explicitly directs the agent to vlr_match for exact UTC starts and to vlr_results for finished matches, giving clear alternatives and conditions for each.

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