Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_results

Fetch completed Valorant match results from VLR.gg, newest first, with final series scores, winners, event, stage, and stats/VOD availability.

Instructions

VLR.gg completed Valorant match results. Returns completed Valorant matches from VLR.gg, newest first, 50 per page, with final series scores, winner flags, event, stage and whether stats or VODs are listed. For a completed match eta is the time since it ended. Use vlr-match with a returned id for map-by-map player statistics.

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 ordering (newest first), page size (50 per page), the record fields returned, and the non-obvious semantic that `eta` means time-since-end for completed matches. It omits anything about rate limits, caching, or whether the result set is bounded, which would matter for an unannotated tool.

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 short sentences, front-loaded with what the tool returns before the payload detail and the sibling handoff. The opening clause 'VLR.gg completed Valorant match results' mildly restates the first sentence's content, a small redundancy in an otherwise tight description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so enumerating returned fields, the pagination unit, sort order, and the meaning of `eta` is exactly what is needed. The handoff to vlr_match covers the obvious next step an agent would want after reading the list, leaving nothing material missing for correct invocation.

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 the baseline would be 3, but the description adds real value the schema does not: the page size is fixed at 50, which tells the agent how to compute offsets from the single `page` parameter. It does not say whether an out-of-range page errors or returns empty.

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 completed Valorant matches from VLR.gg') with scope baked in: completed only, newest first, 50 per page. The enumerated payload fields (final series scores, winner flags, event, stage, stats/VOD flags) let an agent distinguish it from sibling listing tools like vlr_matches or vlr_event_matches 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 Guidelines4/5

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

Gives clear selection context (this is the completed-match feed) and explicitly routes to the alternative: 'Use vlr-match with a returned `id` for map-by-map player statistics.' It stops short of naming exclusions such as upcoming/live fixtures, so the agent must infer that from 'completed' rather than being told.

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