Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bonhams_auction_lots

Retrieve a Bonhams auction's lot listing, filtered by department or free-text query, to inspect or search sale items.

Instructions

List the lots in a Bonhams auction. Returns the lot listing for one Bonhams auction, optionally filtered by department and/or a free-text query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search across lot title, catalog description, and footnotes
idYesBonhams auction id
pageNo1-based page number, default 1
per_pageNoResults per page, default 48, max 100
departmentNoComma-separated department names (not a fixed enum -- varies per auction)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 behavioral burden. It discloses that results are a listing scoped to one auction and optionally filtered, but says nothing about pagination behavior, result caps, or return shape. For a read-only list tool this is acceptable but thin.

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?

Two tight sentences with the core action front-loaded and the filtering caveat following. No wasted text, though the second sentence largely restates the first.

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 no output schema and no annotations, the description should ideally cover pagination defaults or the return structure. It covers scope and filters but leaves the agent to consult the schema for paging and gives no sense of what a lot entry contains.

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 all five parameters (q, id, page, per_page, department) are already documented in the schema. The description echoes the department and free-text filtering but adds no syntax or format detail beyond the schema, matching the baseline 3.

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 (list) and resource (lots in a Bonhams auction) plus the scope of returning one auction's lots. This distinguishes it reasonably from bonhams_lot_search (cross-auction search) and bonhams_auction_detail, though it never names those siblings explicitly.

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?

Phrase 'for one Bonhams auction' implies the id requirement and single-auction scope, and it notes optional department/query filtering. However there is no explicit when-to-use guidance or routing to bonhams_lot_search vs bonhams_auction_lots, leaving the choice 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