Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goldin_auctions

List every Goldin auction since 2012 with title, type, status, start/end dates, and buyer's premium. Pass an auction ID to goldin-search to view its lots.

Instructions

List Goldin's full auction history. Goldin's complete auction event history, back to 2012 -- title, type, status, start/end window, and buyer's premium for every auction Goldin has run. Pass an auction's own id as auction_id to goldin-search to browse its lots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNoasc (oldest first) or desc (newest first, default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It does a solid job: 'List' signals a read operation, and it states the historical scope ('back to 2012') and the exact fields returned. It does not mention pagination, response shape, or rate limits, but for a simple zero-required-parameter listing tool those are secondary.

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?

Three sentences with distinct jobs: state the operation, specify the returned data and scope, and hand off to the sibling tool for lot-level lookup. It is front-loaded and contains no filler.

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 tool with one optional parameter and no output schema, the description is nearly complete: it names the scope, the returned fields, and the next appropriate tool. A bit more detail about response shape or pagination would make it fully self-contained.

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?

The only parameter, order, is fully documented in the schema with enum values and the default behavior ('desc'). The description adds no extra parameter-level detail beyond what the schema already provides, so the baseline 3 applies under high schema coverage.

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 opens with a concrete verb+resource: 'List Goldin's full auction history.' It then specifies the returned fields (title, type, status, start/end window, buyer's premium) and clearly distinguishes this auction-level tool from goldin-search, which browses lots.

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 intended use is clear: retrieve the complete auction-level history when that scope is needed. It explicitly routes the caller to goldin-search for lot-level browsing by auction_id, but it does not spell out exclusions or when other Goldin siblings such as goldin_categories or goldin_listing would be more appropriate.

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