Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

vlr_rankings

Read-only

Returns VLR.gg's Valorant team ranking for one region with rank, team id and name, country, rating, record, streak, earnings and last match id. region is north-america (default), europe, brazil, asia-pacific, korea, china, japan, la-s, la-n, oceania, mena, gc or collegiate; limit 1 to 250 (default 50). Use vlr_team with a returned team id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoOptional number of top-ranked teams to return, 1 to 250; defaults to 50.
regionNoOptional ranking region: north-america (default), europe, brazil, asia-pacific, korea, china, japan, la-s, la-n, oceania, mena, gc or collegiate.

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. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, external nature is covered. The description adds useful field-level return context and the region/limit bounds, but says nothing about caching, rate limits, or snapshot freshness. Adequate but not rich given the structured coverage already present.

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?

Front-loads the core action, then packs parameter bounds and a routing hint into two tight sentences with no wasted wording.

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?

Output schema exists so return values need no explanation, annotations cover the safety profile, and both parameters plus the follow-up path are addressed. Nothing an agent needs to invoke it correctly is 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% and both parameters are fully documented there; the description simply restates the region enum list and the 1–250 limit range with the same defaults. Baseline 3 applies since the schema carries the semantics.

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 (Returns) and resource (VLR.gg Valorant team ranking for one region) and enumerates the returned fields, so an agent knows exactly what it gets. It is clearly distinguishable from sibling team-detail tools like vlr_team.

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?

Explicitly routes the agent to vlr_team with a returned team id, establishing the follow-up flow. It does not state when-not to use it (e.g., versus match/stats tools), but the intended context is clear.

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