Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bonhams_auction_search

Search and filter Bonhams auctions by keyword, status, category, country, and type. Access upcoming or historical auction data from Bonhams' public search API.

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

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.3/5.0
Behavior3/5

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

There are no annotations, so the description must carry the burden. It discloses that the data is 'credential-free public data from bonhams.com's own search API,' indicating no authentication is needed and the tool is read-only. It also clarifies the default behavior. However, it does not mention rate limits, error handling, or response format, which are relevant for a search tool.

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 description opens with a clear purpose, but the second sentence 'Searches and filters Bonhams' auctions' is redundant with the first. The remaining sentences provide valuable context about status and data source, but the redundancy wastes a sentence, preventing a higher score.

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?

The tool has 8 parameters and no output schema, so the description should help an agent understand the search scope and return expectations. It explains the status default and data source, but does not describe what the returned auction data looks like or how to appropriately combine filters. Given the parameter count, more guidance would be helpful.

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 baseline is 3. The description adds context for the status parameter by explaining what 'upcoming' vs 'past' return, which goes slightly beyond the schema's brief 'Filters by bidding/completion status.' This is helpful but limited to one parameter.

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 'Search Bonhams auctions' and 'Searches and filters Bonhams' auctions,' clearly identifying the resource and action. However, it does not explicitly differentiate from sibling tools like bonhams_lot_search or bonhams_auction_detail, so the agent must rely on the name for sibling differentiation.

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 provides guidance on the status parameter, explaining that 'upcoming' is the default and excludes ended auctions, while 'past' browses the historical archive. This is useful internal guidance, but it does not mention alternative tools or when to use them (e.g., bonhams_auction_detail for individual auction details), so alternatives are left to inference.

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