Skip to main content
Glama

Bonhams Lot Details

bonhams_lot_details
Read-onlyIdempotent

Full detail for one Bonhams lot: description, condition, images, realized price (hammer + buyer's premium), estimate range, sale date. Needs the auction_id and lot_no from bonhams_results_search (slug is optional, any slug works as long as auction_id/lot_no match).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lot_no": "8416",
      "auction_id": "14786"
    },
    "name": "bonhams_lot_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoOptional URL slug. Any value works; omit to use a placeholder.
lot_noYesLot number, e.g. "8416" (from bonhams_results_search's lot_no field).
auction_idYesAuction id, e.g. "14786" (from bonhams_results_search's auction_id field).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful context by explaining that the slug is irrelevant and that auction_id/lot_no are the true keys, which prevents failed calls, but it does not describe failure behavior when a lot or auction ID does not match.

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. The returned fields are front-loaded, and the identifier and slug requirements follow immediately after.

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 read-only single-record tool with no output schema, the description effectively substitutes by listing the returned fields, and it documents parameter provenance. The one gap is the absence of any statement about error or not-found behavior on an invalid auction_id/lot_no pair.

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 three parameters are already documented, including that slug can be any value and may be omitted. The description reinforces the key-matching constraint (auction_id and lot_no must match) but adds little beyond what the schema states.

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 names a specific verb and resource ('Full detail for one Bonhams lot') and then enumerates exactly what is returned: description, condition, images, realized price with hammer plus buyer's premium, estimate range, sale date. That enumeration clearly separates it from bonshams_results_search, which is cited as the place the identifiers come from.

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?

It states the prerequisite clearly: auction_id and lot_no must come from bonhams_results_search, and the slug is optional. This documents the expected two-step flow (search, then fetch detail), but it never explicitly says when NOT to use it, for example, when only a list of lots is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.