Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bonhams_lot_search

Search Bonhams lots across current and historical auctions, including sold prices, filtered by department, country, GBP estimate range, or keyword.

Instructions

Search Bonhams lots across every auction. Searches Bonhams lots across every auction, current and historical -- including sold/prices-realized lots -- optionally filtered by department, country, a GBP-normalized estimate price range, and/or a free-text query, in a caller-selected sort order. Without a query and without an explicit sort, results are ordered by most recently active sale date first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search across lot title, catalog description, and footnotes
pageNo1-based page number, default 1
sortNoResult order. Default: Typesense relevance ranking when q is set, otherwise recency (most recently active sale date first).
countryNoComma-separated country names (not a fixed enum -- live facet)
per_pageNoResults per page, default 48, max 100
departmentNoComma-separated department names (not a fixed enum -- large, changes over time)
max_price_gbpNoMaximum estimate, in GBP (converted from each lot's own sale currency), inclusive. Omit or 0 for no maximum.
min_price_gbpNoMinimum estimate, in GBP (converted from each lot's own sale currency), inclusive. Omit or 0 for no minimum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "recency",
+  "price_high",
+  "price_low",
+  "lot_number"
+]
  2. Addedv1.16.2

TDQS

A3.6/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 burden and does disclose meaningful behavior: coverage of current AND historical lots plus sold/prices-realized lots, GBP-normalized estimate pricing, and the default ordering (most recently active sale date) when no query or sort is given. It omits pagination limits and any auth/rate-limit context, so it is strong but not complete.

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 first sentence ('Search Bonhams lots across every auction.') is verbatim redundant with the opening clause of the second sentence, wasting space. The substantive content is reasonably front-loaded but the duplication hurts an otherwise efficient passage.

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 an eight-parameter search tool with full schema coverage and no output schema, the description covers scope, filters, and default result ordering well enough to call it correctly. The absence of sibling differentiation is the main remaining gap.

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 the schema already documents all eight parameters including the sort enum and GBP price semantics. The description restates the filter categories (department, country, price range, query, sort) but adds no syntax or format detail beyond the schema, 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 ('Search Bonhams lots') with an explicit scope ('across every auction, current and historical'). It does not explicitly differentiate from siblings like bonhams_auction_lots or bonhams_lot_detail, so an agent must infer the distinction from the name and scope phrasing.

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 implies the tool's role (cross-auction lot search with optional filters) but never says when to use it versus bonhams_auction_search, bonhams_auction_lots, or bonhams_lot_detail. Usage must be inferred from scope wording rather than an explicit when/when-not statement.

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

Deploy Server

Other Tools