Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_player

Fetch a VLR.gg Valorant player's profile, agent statistics, team history, and recent results by numeric player ID.

Instructions

VLR.gg Valorant player profile and agent statistics. Returns one VLR.gg player: alias, real name, country, social links, agent-by-agent statistics (use, rounds, rating, ACS, K:D, KAST, ADR, KPR, APR and first kills), current and past teams and recent results.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric VLR player id from vlr-team or vlr-stats
timespanNoWindow of the agent statistics; one of all, 30d, 60d, 90d; omit for the site default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return payload in detail and the word "Returns" implies a read-only lookup, but it says nothing about data freshness, whether the timespan window also affects the teams/results sections, or what happens with an invalid id.

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 front-loaded sentences with the identity of the tool stated first and the payload second; nothing is redundant. The long parenthetical stat list (ACS, K:D, KAST, ADR, KPR, APR, first kills) is dense but earns its place by telling the agent which metrics are available without an output schema.

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 no output schema and no annotations, the description compensates well by enumerating the returned sections (identity, social links, agent stats, teams, recent results), which is what an agent needs to judge fit. Missing only behavioral caveats such as error handling and the exact effect of the timespan window.

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%: the id parameter already documents that it is a numeric VLR id sourced from vlr-team or vlr-stats, and timespan documents its enum values. The description's only parameter-adjacent claim ("agent-by-agent statistics") does not clarify that timespan scopes exactly that section, so it adds no meaning beyond the schema.

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 opens with a specific verb-resource pairing ("Returns one VLR.gg player") and scopes it to a single player profile, which cleanly separates it from siblings like vlr_player_matches (match lists) or vlr_team. It then enumerates the payload fields, so an agent knows exactly what data this tool produces without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for fetching a player profile by id. There is no explicit statement of when to prefer it over vlr_player_matches, vlr_stats, or vlr_search, and no mention of prerequisites for obtaining the numeric id beyond what the schema already says.

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