Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_team

Fetch a VLR.gg Valorant team profile by numeric ID, including roster, staff, recent match scores, results, and related news.

Instructions

VLR.gg Valorant team profile and roster. Returns one VLR.gg team: name, tag, country, links, the roster (players with captain flag, plus coach, manager and analyst staff, each with a player id) and recent matches with scores and results, plus related news. Use vlr-player with a roster id.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric VLR team id from vlr-rankings, vlr-event or vlr-match

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it enumerates the returned fields, distinguishes player/staff roles, and mentions recent matches plus news. It doesn't cover error behavior, rate limits, or explicitly state read-only safety, but for a lookup tool the disclosure is substantial.

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 purpose, then return details, then a single handoff note. Every sentence adds distinct information without repetition or filler.

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?

For a single-parameter lookup with no output schema, the description is complete: it explains what is returned in enough detail to know whether the tool fits a query and how to use the roster ids downstream.

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 description coverage is 100%, so the schema already explains that `id` is a numeric VLR team id sourced from vlr-rankings, vlr-event, or vlr-match. The description adds no additional meaning about the input parameter, relying entirely on 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 (Returns) and resource (one VLR.gg team profile and roster), and clarifies scope by naming the exact fields returned. This makes it distinguishable from adjacent tools like vlr_team_matches or vlr_team_maps without opening their schemas.

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?

Gives an explicit alternative for player-related follow-ups ('Use vlr-player with a roster `id`'), but does not explicitly say when to use this tool versus vlr_team_matches or vlr_team_maps. The context is clear, but the exclusion is only implied.

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