Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pristine_auction_search

Search Pristine Auction's live sports card and memorabilia lots by keyword, category, price, or auction status. Filter, sort, and page through active bids or completed sold prices.

Instructions

Search Pristine Auction's live auction inventory. Browses or searches pristineauction.com's current sports card and memorabilia auction lots. term or category is required, matching pristineauction.com's own search form. All enum values (category, auction_type, sort, status) come from pristine-auction-categories. status=completed browses ended/sold lots (a prices-realized view); the default (all statuses) mirrors the site's own default. Every filter is optional and combines with AND semantics.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number, default 1
sortNoResult order, default newly-listed.
termNoFree-text search across lot titles. term or category is required.
statusNoComma-separated auction-status filter. status=completed browses ended/sold lots. Omit to include every status.
categoryNoOne value from pristine-auction-categories' categories[].slug. term or category is required.
per_pageNoResults per page. pristineauction.com only accepts 15, 30, or 60; any other value is rejected. Default 30.
max_priceNoMaximum current bid price in USD, inclusive. Omit or 0 for no maximum.
min_priceNoMinimum current bid price in USD, inclusive. Omit or 0 for no minimum.
auction_typeNoComma-separated auction-type filter. Omit to include every auction type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the conditional requirement (term or category), the enum provenance (pristine-auction-categories), the meaning of the default status set, and AND-combination of filters. It omits return/pagination behavior, but for a read-only search that is a minor gap.

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 and scoping requirement in the first two sentences, then adds behavioral notes. Every sentence earns its place, though the enum-provenance and default-behavior sentences could be tightened slightly.

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 9-parameter, annotation-free search with no output schema, the description covers the essentials: requirement rules, defaults, enum source, filter combination, and the special status=completed semantics. Return format and pagination are left to the schema, which is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds genuine value beyond the schema by explaining that enums are sourced from pristine-auction-categories, that term/category is a conditional requirement absent from the empty required array, and that filters combine with AND.

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 (search) and resource (Pristine Auction's live sports card and memorabilia auction lots), and explicitly ties it to pristineauction.com's own search form. It is clear what the tool does, though it does not differentiate itself from adjacent siblings like pristine_auction_lot or goldin_search.

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?

Gives concrete usage conditions: term or category is required, every other filter is optional, filters combine with AND semantics, and status=completed selects ended/sold lots. It stops short of naming alternative tools or when-not-to-use cases, so it is clear context without explicit 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