Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora.mcp
OverviewDiscussionsAdmin

vlr_forum_threads

Read-only

Returns a page of 30 VLR.gg forum threads, newest activity first, for one category (valorant-discussion, off-topic, site-feedback) or all categories: title, reply count, pinned flag, author, post age, frags and last poster. Optional category, sort (hot, new or top; default recent activity) and page. Only list metadata is returned, not post bodies. Use vlr_forum_categories for category counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vlr_forum_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional 1-based page; defaults to 1.
sortNoOptional order: hot, new or top; omit it for the site default (recent activity).
categoryNoOptional forum category slug from vlr_forum_categories: valorant-discussion, off-topic or site-feedback. Omit for the combined thread list.

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 / sort
      Added value: +{
+  "description": "Optional order: hot, new or top; omit it for the site default (recent activity).",
+  "type": "string"
+}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, so credit goes to added detail: fixed page size of 30, newest-activity-first default ordering, and the explicit statement that post bodies are not included. Pagination semantics (1-based page) are covered by the schema, not repeated here.

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 dense sentences, front-loaded with the resource, page size, and ordering before options and the sibling pointer. No filler or redundant restatement of the tool name.

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?

An output schema exists, so return values needn't be explained; for a three-optional-parameter read tool this covers scope, ordering, page size, and the key limitation (no post bodies). Nothing needed to call it correctly is missing.

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 the schema already documents the category slugs, the hot/new/top sort values, the recent-activity default, and 1-based paging. The description restates these lists with no additional syntax, constraints, or interaction rules (e.g., whether sort interacts with category), so it does little beyond the schema baseline.

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 concrete verb+resource ('Returns a page of 30 VLR.gg forum threads'), the ordering, and the scope (one category or all). It also enumerates the fields returned and names the sibling tool it is not (vlr_forum_categories), so an agent can distinguish it without opening a schema.

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?

Explicitly routes category-count queries to vlr_forum_categories and clarifies that only list metadata comes back, not post bodies, which tells the agent this is a browsing tool rather than a content-read tool. It doesn't name a sibling to use for actual post content, so the exclusion is stated but the alternative isn't.

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