Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

slickdeals_forums

Read-only

Slickdeals' full legacy sub-forum list (e.g. Hot Deals, Coupons, Freebies) -- the discovery source for slickdeals_search's forum_id param, and the way to resolve the forum_id already returned by slickdeals_deal/slickdeals_search_advanced/slickdeals_frontpage to a human-readable name. A different, coarser-grained taxonomy from slickdeals_categories' 421-entry tag list. Optional q substring-filters by name.

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

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive substring filter on name

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 / q / description
      Added value: +"Case-insensitive substring filter on name"
  2. First observed

TDQS

A4.4/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 the safety profile is covered. The description adds genuinely useful context beyond that: this is a legacy/static taxonomy, the discovery role it plays for other slickdeals tools, and the 'full list' scope. It does not cover pagination or rate limits, but for a static taxonomy read the omission is minor.

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?

Front-loads the core identity before the relational details, and every sentence carries information. Slightly dense with em-dash clauses and the '421-entry' figure is borderline trivia, but nothing is truly wasted.

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 described. The description covers identity, scope, sibling differentiation, and both directions of the forum_id relationship — enough for an agent to call it correctly.

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%, so the schema already documents q. The description's 'Optional q substring-filters by name' adds nothing the schema doesn't already say (in fact it drops the 'case-insensitive' detail). Baseline 3 is correct when the schema does the heavy lifting.

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 the specific resource ('full legacy sub-forum list') and immediately distinguishes it from the sibling slickdeals_categories ('a different, coarser-grained taxonomy'). An agent can identify what this returns without opening the schema.

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

Usage Guidelines5/5

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

Explicitly names two use cases: discovering the forum_id needed by slickdeals_search, and resolving a forum_id returned by slickdeals_deal/slickdeals_search_advanced/slickdeals_frontpage into a name. It also names the competing taxonomy tool and the axis of difference, so when-to-use vs. alternatives is unambiguous.

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