Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vlr_forum_threads

Retrieve paginated VLR.gg forum thread listings by category or combined, sorted by hot, new, top, or recent activity, with titles, replies, authors, scores, and last poster.

Instructions

VLR.gg forum thread list. Returns a page (30) of VLR.gg forum threads, newest activity first, for one category (valorant-discussion, off-topic, site-feedback) or the combined list: title, reply count, pinned flag, category, author, post age, frags (score) and the last poster. Thread titles and usernames are public community content; thread bodies and replies are not returned.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number; defaults to 1
sortNoOrder; one of hot, new, top; omit for the site default (recent activity)
categoryNoForum category; one of valorant-discussion, off-topic, site-feedback; omit for the combined list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/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 the fixed page size (30), default ordering (newest activity first), the exact fields returned, and an important scope limit — thread bodies and replies are not returned, so only titles/usernames are exposed. It stops short of stating pagination bounds, rate limits, or how pinned threads interact with ordering.

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?

Two tight sentences: the return contract comes first, then the field list and the body/reply exclusion. No filler, nothing repeated beyond a slight overlap between 'newest activity first' and the schema's default-sort note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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's enumeration of returned fields (title, replies, pinned, category, author, post age, frags, last poster) is exactly the missing context an agent needs. Completeness would be higher with pagination limits or a pointer to the categories sibling.

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 enum parameters are self-documenting, so the baseline is 3. The description reinforces the meaning of `category` (omit for combined list) and repeats the default ordering, but only the page-size detail genuinely adds information beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource and verb ('VLR.gg forum thread list. Returns a page (30) of VLR.gg forum threads') and delimits scope (one category or the combined list). It is clearly distinct from the sibling vlr_forum_categories, but never names that sibling explicitly, leaving the differentiation to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the agent can infer it should call this to browse forum threads and that omitting `category` yields the combined list. There is no explicit 'use this when' guidance, no when-not conditions, and no pointer to alternatives such as vlr_forum_categories or a thread-detail tool.

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