Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

vlr_player

Read-only

Returns one VLR.gg Valorant player by numeric id (optional timespan all, 30d, 60d or 90d for the agent statistics): alias, real name, country, social links, agent-by-agent stats (use, rounds, rating, ACS, K:D, KAST, ADR, KPR, APR, first kills), current and past teams and recent results. Get ids from vlr_team or vlr_stats. Use vlr_stats for filtered, league-wide stat tables.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired numeric VLR player id from vlr_team or vlr_stats.
timespanNoOptional window of the agent statistics: all, 30d, 60d or 90d; omit it for the site default.

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 / timespan
      Added value: +{
+  "description": "Optional window of the agent statistics: all, 30d, 60d or 90d; omit it for the site default.",
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only/open-world semantics, and the description adds that the optional timespan only affects agent statistics and that team/results history is bundled in. No mention of caching, rate limits or missing-player behavior, but the bar is lower given annotation coverage and an output schema.

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?

Two sentences, front-loaded with what is returned before the id-sourcing and sibling-routing guidance. The long parenthetical stat list is slightly dense but earns its place by telling the agent what fields exist.

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?

With only two parameters, full schema coverage, and an output schema covering return structure, the description supplies everything needed: id provenance, timespan effect, and the sibling alternative. Minor gap: no note on what happens for an invalid or non-numeric id.

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, but the description adds meaning beyond the schema by stating the timespan scope (all/30d/60d/90d governs the agent-stats window only) and by tying the id format (numeric) to its source tools.

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 one VLR.gg Valorant player'), specifies the id type (numeric) and enumerates the payload (alias, country, socials, agent stats, teams, recent results). It is clearly distinguishable from siblings like vlr_players search or vlr_stats tables.

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 ids come from ('Get ids from vlr_team or vlr_stats') and names the alternative route ('Use vlr_stats for filtered, league-wide stat tables'), so the agent knows both the precondition and when not to call this tool.

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