Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_news_article

Retrieve a VLR.gg news article by numeric ID, returning its title, author, UTC publish time, plain-text body, linked teams, players, events, external links, and image URLs.

Instructions

VLR.gg news article. Returns one VLR.gg news article: title, author, UTC publish time, the body as plain-text paragraphs, the teams, players and events it links to (type team, player or event, with id, slug and name), external links and image URLs. Reader comments are not included. Forum threads share the same numeric id space, so an id that is a thread, or does not exist, returns not found. Take id from vlr-news.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric VLR news article id from vlr-news

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that reader comments are excluded from the result and that the shared numeric id space with forum threads produces a not-found outcome. It omits auth/rate-limit behavior and truncation/body-size limits, which keeps it short of 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 tight sentences: what it returns, what it omits, and the id caveat. Return contents come first, no filler, and the exclusion/edge-case notes are compressed into short clauses.

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?

There is no output schema, so the description compensates by enumerating the response shape (including nested linked-entity types with id/slug/name) and by flagging the comments exclusion and the not-found case. An agent has everything needed to call it and interpret the result.

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% and the schema already documents the single `id` parameter, so baseline is 3. The description adds value by explaining the id's provenance (from vlr-news) and the collision hazard with forum thread ids, which the schema does not state.

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?

Opening sentence names the specific resource and verb ('Returns one VLR.gg news article') and immediately enumerates the returned fields (title, author, UTC publish time, plain-text body, linked teams/players/events, external links, images). This clearly distinguishes it from the sibling list tool vlr_news and from vlr_forum_threads, which it explicitly warns about.

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?

It states the prerequisite for the id ('Take `id` from vlr-news') and gives a concrete failure condition: ids belonging to forum threads or nonexistent ids return not found. It stops short of naming the sibling to call for listing articles, but the pointer to vlr-news effectively covers that.

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