Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

bo3_forum

Read-only

Returns BO3.gg forum threads for one game with paging: category (an id from bo3_forum_categories) and sort (activity with pinned 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 nickname; post bodies are not returned. Use bo3_forum_categories first to find a category id.

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": "bo3_forum"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoOptional game: cs2 (default), valorant, lol, dota2, r6siege or mlbb.
sortNoOptional order: activity (default, pinned first), newest, comments or rating.
limitNoOptional page size 1 to 100, default 20.
offsetNoOptional zero-based offset, default 0.
categoryNoOptional forum category id from bo3_forum_categories.

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. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds the paging contract (up to 100 per page) and the negative disclosure that post bodies are absent, which prevents a wasted call expecting thread text. It stops short of stating total-count/has-more behavior or any 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.

Conciseness5/5

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

Three sentences, no filler: capability and paging first, returned field list second, prerequisite ordering last. Every clause carries actionable information and the routing hint sits where an agent will read it before calling.

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?

For a read-only, open-world list tool with five optional params and an output schema, the description covers what is returned, what is deliberately omitted, the page-size ceiling, and the prerequisite lookup. Nothing an agent needs in order 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 description coverage is 100%, so every parameter (game, sort, limit, offset, category) is already documented in the schema, including defaults and the 1–100 limit. The description largely restates these (sort modes, category provenance, per-page cap) without adding syntax, constraints, or edge cases the schema lacks; baseline 3 applies.

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?

Opens with an explicit verb and resource ("Returns BO3.gg forum threads") and immediately bounds the scope to one game with paging. It also rules out an adjacent capability by stating post bodies are not returned, so an agent can tell it apart from a thread-content tool 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?

Gives one hard prerequisite — "Use bo3_forum_categories first to find a category id" — which is exactly the workflow ordering an agent needs before passing a numeric category. Sort modes are enumerated with their meaning, but there is no explicit statement of when not to use this tool versus the many bo3_* siblings.

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