Fetch current Valorant esports news headlines from VLR.gg, including title, summary, date, author, and country flag; page through older items with the page parameter.
VLR.gg Valorant esports news. Returns the latest Valorant esports news headlines from VLR.gg, 30 per page, with title, summary line, date, author and country flag. Page back through older news with page.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page number; defaults to 1 |
Changes observed during successful MCP inspections.
v1.17.18Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It does disclose useful behavior: 30 items per page and the shape of each record (title, summary, date, author, country flag). It says nothing about whether more pages exist, error behavior, or freshness/rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences: the first identifies source and payload, the second handles pagination. No filler and nothing front-loaded incorrectly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description compensates by listing the returned fields, which is what an agent needs to decide whether to call it. The remaining gap is routing to vlr_news_article for full text, which is a usage concern rather than a completeness blocker.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and there is only one optional parameter, so the baseline is 3. The description goes slightly beyond the schema by explaining the semantic effect of `page` — it walks backward into older news — rather than just restating 'page number'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: returns the latest Valorant esports news headlines from VLR.gg, and enumerates the fields returned. It is distinguishable from vlr_news_article by being a listing rather than a single article, though it never names that sibling explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The only usage guidance is pagination: 'Page back through older news with `page`.' There is no statement of when to use this versus vlr_news_article for full article bodies, or versus vlr_forum_threads/vlr_search. Implied usage only.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.