Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

vlr_team_matches

Read-only

Returns a Valorant team's complete match history from VLR.gg (group=upcoming lists its scheduled matches instead), 50 per page, newest first: event, stage, opponent, series score, win or loss and date. Provide the numeric team id from vlr_rankings, vlr_event or vlr_match and page through has_more. Use vlr_match with a returned id for map detail.

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_team_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 description focuses on added context: 50 results per page, newest-first ordering, and has_more-driven pagination. It doesn't state failure modes or edge cases (e.g., empty history, invalid id), 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?

Three sentences, front-loaded with the core purpose, then the group variation, then id sourcing and paging, then the sibling handoff. Zero waste.

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 fields needn't be explained, yet the description still lists them for orientation. For a paginated read tool with complete param coverage and annotations, nothing an agent needs is missing.

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 schema documents the parameters, but the description adds meaning the schema does not: the id must be a team id sourced from vlr_rankings/vlr_event/vlr_match, and group=upcoming changes the result from history to scheduled matches. That is genuine value 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?

States a specific verb+resource+scope: a team's complete match history from VLR.gg, and explicitly flags the group=upcoming variation. An agent can distinguish it from vlr_match, vlr_player_matches and vlr_team_maps from the description alone.

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 id comes from (vlr_rankings, vlr_event, vlr_match), when to use group=upcoming, how to paginate (page through has_more), and which sibling to call for map detail. Nothing is left to inference.

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