Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bonhams_auction_search

Search and filter Bonhams auction listings by keyword, category, country, month, status, or type to find upcoming sales or browse past archives.

Instructions

Search Bonhams auctions. Searches and filters Bonhams' auctions. Default status "upcoming" excludes ended auctions, matching bonhams.com's own default; "past" browses Bonhams' full historical auction archive instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search across auction title and department names
pageNo1-based page number, default 1
monthNoComma-separated month-and-year values, e.g. \
statusNoFilters by bidding/completion status, default upcoming
countryNoComma-separated country names (not a fixed enum -- live facet)
categoryNoComma-separated categories. Allowed values: 20th & 21st Century Art, Asian Art, Books, History & Science, Classic Art, Decorative Arts & Furniture, Handbags, Jewels & Watches, Motoring, Popular Culture, Wine & Whisky.
per_pageNoResults per page, default 24, max 100
auction_typeNoComma-separated auction types

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / auction_type / enum
      Added value: +[
+  "ONLINE",
+  "PUBLIC",
+  "EXHIBITION",
+  "OTHER"
+]
    • addedInput schema / properties / status / enum
      Added value: +[
+  "upcoming",
+  "past",
+  "all"
+]
  2. Addedv1.16.2

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the default filter behavior (ended auctions excluded by default) and the archive scope of 'past', but says nothing about return shape, pagination beyond the schema's per_page, rate limits, or auth requirements.

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 two sentences are redundant—'Search Bonhams auctions' and 'Searches and filters Bonhams' auctions' restate the same fact. The genuinely informative status sentence is buried third, so the content is not front-loaded and one sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 optional params, no output schema, and no annotations, the description covers the key behavioral nuance (default status filtering) but omits return format, result shape, and how it relates to the other Bonhams tools. Adequate but with clear gaps for an agent deciding between Bonhams endpoints.

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 adds real semantic value on the status parameter by explaining what the default actually excludes and what 'past' retrieves—information the schema's terse 'Filters by bidding/completion status' does not convey.

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?

The description states a specific verb and resource ('Search Bonhams auctions... searches and filters Bonhams' auctions'), making the purpose unambiguous. However, it never names or contrasts against the obvious siblings (bonhams_lot_search, bonhams_auction_detail, bonhams_auction_lots), so an agent must infer the distinction from the resource noun alone.

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?

It provides genuine guidance on the status parameter: the default 'upcoming' excludes ended auctions and 'past' browses the historical archive. But it gives no when-to-use guidance relative to alternative tools (e.g., use this to find auctions, then bonhams_auction_lots for lots), leaving usage only partially implied.

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