Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

vlr_player_matches

Read-only

Returns a Valorant 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. Provide the numeric player id from vlr_team or vlr_stats and page with has_more. Use vlr_match for the player's per-map statistics.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired numeric VLR id (team id for vlr_team_matches, player id for vlr_player_matches).
pageNoOptional 1-based page; defaults to 1.
groupNoOptional, vlr_team_matches only: completed (default) or upcoming.

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. Changed1 schema field changed
    • addedInput schema / properties / group
      Added value: +{
+  "description": "Optional, vlr_team_matches only: completed (default) or upcoming.",
+  "type": "string"
+}
  2. Added

TDQS

A4.7/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 valuable behavior: page size of 50, newest-first ordering, and the has_more pagination signal. It stops short of discussing rate limits or data freshness, so a 4 rather than 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?

Three tight sentences, front-loaded with purpose, then pagination, then the sibling cross-reference. No filler; every clause carries actionable information.

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?

With an output schema present the return shape need not be restated, and annotations cover safety. Combined with the 100% schema coverage, the description supplies everything else an agent needs: id provenance, ordering, page size, and pagination 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 the baseline is 3. The description goes beyond the schema by explaining that id is a numeric player id sourced from vlr_team/vlr_stats, which clarifies an otherwise ambiguous 'id' field, and by tying page to the has_more flag.

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 a Valorant player's match history from VLR.gg') plus scope details (50 per page, newest first) and enumerates the returned fields. It also distinguishes itself from the sibling vlr_match, so an agent can pick correctly without opening schemas.

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 says where the required id comes from ('from vlr_team or vlr_stats'), how to paginate ('page with has_more'), and names the alternative for per-map data ('Use vlr_match for the player's per-map statistics'). All routing decisions are spelled out.

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