SiteCheck Shop & Social

Auction lots from Invaluable for a keyword: upcoming lots

ecommerce_invaluable_auctions

Read-only

Auction lots from Invaluable (thousands of auction houses worldwide) for a keyword: upcoming lots with current bid, bid count, estimate range, sale date and type (live/timed), or past lots with the hammer price result. Each lot: title, lot number, category path, artist, auction house, location and country, currency, image and lot URL; plus the total matching lots. Bidder identities are not returned. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "ecommerce_invaluable_auctions"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Keyword, e.g. rolex, picasso, tiffany lamp (required)
`page`	No	Page number from 1 (default 1)
`limit`	No	Lots per page, 1 to 50 (default 20)
`status`	No	upcoming (default) or past

Output Schema

Name	Required	Description	Default
`q`	No
`lots`	No
`page`	No
`count`	No
`total`	No
`source`	No
`status`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only say readOnly and openWorld; the description adds substantial context beyond that: bidder identities are excluded, total matching lots are returned, and the call is metered at $0.002 USDC via x402 with failed calls uncharged. The pricing/payment-rail detail is the kind of operational fact an agent must know before calling, though it does not discuss rate limits or result-size ceilings.

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?

A single dense paragraph that front-loads the resource and mode split, then enumerates returned fields and closes with the cost/limitation caveats. No filler sentences; every clause carries information an agent would act on.

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 paid, paginated, read-only search across auction houses, the description covers what it searches, both result modes, the fields returned, the exclusion of bidder identities, the total count, and the exact billing model. Nothing needed 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by tying the status values to materially different payloads (current bid, bid count, estimate, sale date, live/timed vs hammer price) and by noting the total matching count that accompanies pagination. It still says nothing extra about page/limit beyond the schema.

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 resource (auction lots from Invaluable) plus the retrieval axis (keyword) and the two modes (upcoming vs past). The clause 'thousands of auction houses worldwide' plus the enumerated lot fields make it unmistakable against every sibling, none of which cover auction houses.

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

Usage Guidelines3/5

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

The description explains what each value of status yields (upcoming with current bid/bid count; past with hammer price), which is genuine when-to-use guidance for the mode choice. However, it never names an alternative tool or states when-not to use it, so tool-selection guidance is only implied by domain.

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

All SiteCheck Shop & Social 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?