Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bonhams_lot_search

Find Bonhams lots across all auctions, past and present, including sold prices. Filter by department, country, price estimate, or keyword, and sort by relevance, recency, or price.

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. Credential-free public data from bonhams.com's own search API.

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

A4.1/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. It discloses that data is credential-free and public, includes sold lots, and explains default ordering behavior when no query or sort is provided. It does not mention pagination or rate limits, but for a read-only search, these are minor gaps. No contradiction with annotations since none exist.

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?

The description is two sentences but repeats 'Searches Bonhams lots across every auction' at the start, which is redundant. However, the information is front-loaded and the details are efficiently packed. Minor redundancy prevents a perfect score.

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 search tool with 8 parameters all documented in the schema and no output schema, the description covers the essential context: scope (all auctions), available filters, default sort behavior, and credential-free access. It doesn't detail pagination mechanics but those are in the schema. It is complete enough for an agent to call 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 the schema already documents all parameters thoroughly. The description repeats filter types (department, country, price range, query, sort) but adds no extra meaning beyond what the schema provides. It does clarify the default ordering, which is slightly beyond the schema, but that is minor. Baseline 3 is appropriate.

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?

The description clearly states the tool searches Bonhams lots across every auction, both current and historical, including sold/prices-realized lots. It specifies the action (search), resource (Bonhams lots), and scope, distinguishing it from siblings like bonhams_auction_search or bonhams_auction_lots which target specific auctions or lists.

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?

The description provides clear context: it is the global search across all auctions, with optional filters. It does not explicitly name alternatives or when not to use it, but the scope ('every auction') implicitly signals when this tool is appropriate. It lacks explicit exclusions but is not misleading.

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