Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_player_matches

Retrieve a Valorant player's VLR.gg match history by numeric player ID, paginated newest first with event, teams, series score, result, and date; use returned match IDs for map stats.

Instructions

VLR.gg Valorant player match history. Returns a player's match history from VLR.gg, 50 per page, newest first: event, stage, the player's team and opponent, series score, win or loss and date. Use vlr-match with a returned id for the player's map statistics.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric VLR player id from vlr-team or vlr-stats
pageNo1-based page number; defaults to 1

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 behavioral burden and does well: it discloses pagination size (50 per page), ordering (newest first), and the returned fields. It does not mention rate limits or whether the operation is strictly read-only, which keeps it from a 5.

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?

The description is front-loaded and compact: the core resource comes first, followed by return details and the sibling hand-off. Every sentence earns its place.

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?

For a two-parameter list tool with no output schema, the description supplies enough return-shape detail and a clear next-step tool. Nothing an agent needs in order to call this correctly appears to be missing.

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 `id` and `page` are already documented. The description reinforces paging behavior by stating '50 per page' and 'newest first,' but it does not add new meaning to the `id` parameter beyond what the schema already says.

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?

The description names a specific verb and resource: returns a Valorant player's match history from VLR.gg. It also distinguishes the output from a sibling by directing map statistics to vlr-match, so an agent can tell what this tool does and does not cover.

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?

It gives a clear follow-up path: use vlr-match with a returned `id` for map statistics. It does not explicitly contrast with other player-history siblings such as vlr_player or vlr_team_matches, so it stops short of full when-to-use guidance, but the context is clear.

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