Crawlora MCP

slickdeals_deal

Read-only

One Slickdeals deal thread's full detail: title, store, final/list price, community vote score, comment count, expired status, category/sub-category taxonomy and legacy forum, the public username who posted it with their community-standing summary, a related-deals sidebar, the outbound merchant link, and description. Give url (from slickdeals_search) or thread_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": "slickdeals_deal"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Full Slickdeals deal URL, as returned by GET /slickdeals/search (https://slickdeals.net/f/...)
`thread_id`	No	Slickdeals numeric thread id

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / thread_id / description
```
Added value: +"Slickdeals numeric thread id"
```

addedInput schema / properties / url / description

Added value: +"Full Slickdeals deal URL, as returned by GET /slickdeals/search (https://slickdeals.net/f/...)"

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior3/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's content is essentially a return-value enumeration, adding little behavioral context beyond the annotations (no auth, rate-limit, or freshness notes). With an output schema present, this enumeration is largely redundant.

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 resource and scope, then closes with the input instruction. The field enumeration is long but every item is a distinct returned attribute; structure is clean with no filler sentences.

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?

An output schema exists, so return values need not be described, and the description covers the two input paths adequately. Since the bulk of the text duplicates schema-covered output, it is slightly over-built on the wrong axis, but nothing needed to call the tool 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 both parameters are already documented with format expectations. The description reinforces provenance ('url (from slickdeals_search)') but adds no syntax or fallback semantics beyond the schema. Baseline 3 applies 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 a specific verb+resource ('One Slickdeals deal thread's full detail') and enumerates the exact fields returned, letting an agent distinguish it from slickdeals_search (list) and slickdeals_comments (comments). The scope is unambiguous.

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?

'Give url (from slickdeals_search) or thread_id' establishes the upstream dependency and the two entry paths, which implicitly tells the agent to use this after a search. It does not state explicit when-not conditions or name a competing detail tool, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

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

Need Help?