Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_forum

Fetch BO3.gg forum threads for a chosen game with category, sort, and paging filters, returning thread titles, stats, and activity times for forum monitoring or analysis.

Instructions

BO3.gg forum threads with category and sort filters. Returns BO3.gg forum threads for one game with paging: a category id from bo3-forum-categories and sort (activity with pinned threads first, newest, comments, rating), up to 100 per page. Each thread has slug, title, category, comment count, rating, pinned flag, created and last-activity times and the author's nickname; post bodies, reactions and replies are not returned.

Input Schema

NameRequiredDescriptionDefault
gameNoGame; one of cs2, valorant, lol, dota2, r6siege, mlbb; defaults to cs2
sortNoOrder; one of activity, newest, comments, rating; defaults to activity
limitNoPage size, 1 to 100; defaults to 20
offsetNoZero-based offset; defaults to 0
categoryNoForum category id from bo3-forum-categories, for example 4

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.4/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 load and does so well: it discloses paging (up to 100 per page), the exact shape of a returned thread, and explicitly what is absent (post bodies, reactions, replies). It does not state read-only nature explicitly beyond 'Returns', nor any rate limit, but the negative-space disclosure is unusually strong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with purpose then the paging contract then the return shape. Minor waste: the first sentence and the second open by restating 'BO3.gg forum threads' almost verbatim.

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?

No output schema exists, and the description compensates by enumerating every returned thread field and calling out the omitted content. Combined with the paging contract and default handling implied by the schema, an agent has everything needed to call this correctly.

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%, so baseline is 3, but the description earns above that by explaining semantics the schema only enumerates: 'activity' orders pinned threads first, and 'up to 100 per page' frames limit/offset paging. The category->bo3-forum-categories dependency is also restated with intent.

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?

Specific verb+resource (returns BO3.gg forum threads), with the scope narrowed to 'one game' and to category/sort filtering. It names the companion tool bo3-forum-categories that supplies the category id, so an agent can distinguish it from the categories lookup without opening either 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?

It states the prerequisites for meaningful use (a category id must come from bo3-forum-categories) and explains the sort modes including the notable 'activity puts pinned threads first' behavior. It gives no explicit when-not-to-use or alternative tool for full-text/post content, which is the only gap.

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