Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

bonhams_lot_detail

Retrieve normalized facts for a Bonhams lot by auction ID and lot number, including title, estimate range, realized price, sale date, category, department, and lot number.

Instructions

Get a Bonhams lot's normalized facts. Returns one Bonhams lot's facts: title, estimate range, hammer/realized price (once sold), sale date, category, department, and lot number. Full lot description prose, condition-report text, and additional images are not reproduced -- see the response fields.

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": {
      "auctionId": "<auctionId>",
      "lotNumber": "<lotNumber>"
    },
    "name": "bonhams_lot_detail"
  }
}

Input Schema

Name	Required	Description	Default
`auctionId`	Yes	Bonhams auction id
`lotNumber`	Yes	Bonhams lot number

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.2Sep 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full load, and it does useful negative-space disclosure: full lot description prose, condition-report text, and additional images are explicitly NOT returned. It also flags conditional behavior ('hammer/realized price (once sold)'). Auth needs and rate limits remain unstated.

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-loaded with the core purpose, then the field list and exclusions. Minor redundancy between 'normalized facts' and 'facts', but overall tight with no wasted 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?

For a two-param read tool with no output schema, the description compensates reasonably by enumerating the returned fields and stating what is omitted. It could say more about the response shape, but an agent has enough 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 description coverage is 100%, so both auctionId and lotNumber are already documented in the schema. The description adds no format or sourcing detail for either parameter, so the baseline 3 applies.

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?

States a specific verb and resource ('Get a Bonhams lot's normalized facts') and enumerates the returned fields (title, estimate range, hammer/realized price, sale date, category, department, lot number). This clearly separates it from bonhams_lot_search, though it never names that sibling explicitly.

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?

Usage is implied by the 'detail' framing and the required auctionId+lotNumber pair, but there is no explicit statement of when to call this versus bonhams_lot_search, bonhams_auction_lots, or bonhams_auction_detail. No prerequisites or exclusions are given.

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

Deploy Server