Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bonhams_auction_detail

Retrieve normalized facts for any Bonhams auction by ID, including title, category, department, country, currency, sale dates, and lot count. Works for historical or ended sales too.

Instructions

Get a Bonhams auction's normalized facts. Returns one Bonhams auction's facts by id: title, category, department, country, currency, sale dates, and lot count. Unlike the search endpoint, this is not restricted to upcoming/live auctions -- a historical/ended auction id resolves too.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesBonhams auction id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does disclose a non-obvious behavior: ended/historical auction ids resolve, unlike the search endpoint. Enumerating the returned facts also substitutes for the absent output schema. It does not cover error/not-found behavior or rate limits, keeping it at 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, and the core purpose is front-loaded before the differentiating detail about historical auctions. Every clause earns its place.

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?

With no annotations and no output schema, the description compensates by listing the returned fields and the key resolving behavior. This is nearly complete for a single-id lookup, with only error/edge-case handling left unstated.

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% and there is a single 'id' parameter already documented as 'Bonhams auction id'. The description adds only the nuance that the id may reference a historical auction; baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb+resource ('Get a Bonhams auction's normalized facts') and enumerates the returned fields, so the agent knows exactly what comes back. It also explicitly distinguishes itself from the search endpoint ('Unlike the search endpoint...'), making it separable from its siblings bonhams_auction_search and bonhams_lot_detail.

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 contrast with the search endpoint ('this is not restricted to upcoming/live auctions -- a historical/ended auction id resolves too') tells the agent precisely when this tool is the right choice over search. It stops short of stating the obvious preconditions (you must already have an auction id), so it is clear context without full exclusions.

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