SiteCheck Crypto & Finance

B-Stock wholesale liquidation auctions: total live lots

finance_bstock

Read-only

B-Stock wholesale liquidation auctions (US marketplace, all sellers): total live lots and 20 per page with listing id, title, storefront (seller), categories, condition, inventory type, units, pallets, manufacturers, current / opening bid, next minimum bid, number of bids, typical selling price, currency, start and end time, seller city/state/zip, shipment type, manifest flag, image and auction link. From bstock.com via a residential proxy. Takes about 19 s; allow a 30 s timeout. Related tools on this server, for a different need: finance_finviz when you need Finviz quote snapshot for one stock ticker: the key; finance_stockanalysis when you need StockAnalysis company identity for one stock ticker. Price: $0.02 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
`page`	No	Result page 1-40 (default 1)
`category`	No	Optional: keep only lots whose categories contain this text, e.g. Cell Phones, Major Appliances

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint: states the data source is bstock.com via a residential proxy, gives expected latency (~19 s) with a concrete 30 s timeout recommendation, and discloses x402 payment mechanics ($0.02 USDC per successful call on Base/Solana/Arc, failures not charged). These are exactly the operational facts an agent needs before invoking.

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

Conciseness3/5

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

The front-loaded scope plus latency/pricing/alternatives sentences are efficient, but the long mid-sentence enumeration of ~20 returned fields is low value given an output schema already exists and it buries the actionable operational facts.

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?

With an output schema present, return values needn't be explained, and the description covers cost, latency, timeout, source and alternatives, which is enough to call it correctly. Its main redundancy is re-listing return fields the output schema already defines.

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 both parameters are already documented; baseline 3 applies. The description adds '20 per page', which clarifies the paging granularity of the page parameter, but says nothing about the category text filter beyond listing 'categories' among returned fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource with scope: 'B-Stock wholesale liquidation auctions (US marketplace, all sellers): total live lots and 20 per page'. An agent knows exactly what data it gets and the page size, though the verb is implicit and the sentence then drifts into a field inventory rather than staying on purpose.

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 separates itself from the two neighboring finance tools by naming them and the distinct need each serves (Finviz ticker snapshot, StockAnalysis company identity). It doesn't state exclusions or prerequisites for this tool itself, but there are no close alternatives to disambiguate against.

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

All SiteCheck Crypto & Finance 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?