Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pristine_auction_lot

Fetch complete details for a Pristine Auction lot using its lot number—including title, images, current or sold price, end time, category, and bid counts.

Instructions

Get a Pristine Auction lot's full detail. Returns one pristineauction.com lot's full detail: title, description, image gallery, price (current high bid, or realized/sold price once the auction has ended), auction end time, sport/collectible category, auction type, no-reserve flag, and view/watch/bid counts. lot_number comes from pristine-auction-search's results[].lot_number.

Input Schema

NameRequiredDescriptionDefault
lot_numberYesA lot_number from pristine-auction-search's results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 disclosure burden. It adds one genuinely useful behavioral note (price reflects the current high bid, or realized/sold price once the auction ends) and enumerates the return shape in place of an output schema, but says nothing about permissions, rate limits, or error behavior.

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?

Front-loads the core purpose, then the return fields, then the parameter provenance — a sensible order with little waste. The field enumeration is slightly list-heavy but each item adds information an agent cannot get elsewhere.

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 output schema and no annotations, the description compensates by enumerating the returned fields and noting the price semantics, and it explains how to source the required parameter. That is close to complete for a single-parameter detail tool, though auth/error context is absent.

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 coverage is 100% and the single parameter's description already says it comes from pristine-auction-search's results, so the description's mention of the provenance is largely redundant with structured data. Baseline 3 is appropriate when the schema already documents the only parameter.

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 Pristine Auction lot's full detail') and enumerates the exact fields returned, so the scope is unambiguous. It also names the sibling tool for obtaining the identifier, distinguishing it from pristine_auction_search and pristine_auction_categories.

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?

Explicitly tells the agent where the required lot_number comes from ('pristine-auction-search's results[].lot_number'), which is the key usage precondition. It stops short of stating when not to use this tool, but the routing to the search tool is clear.

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