Skip to main content
Glama

Us Auctions Sold Comps

us_auctions_sold_comps
Read-onlyIdempotent

Historical SOLD prices for US auction items, the final hammer price of closed lots, which no upstream site keeps but Pipeworx retains across both the commercial and government halves of the market. Use to answer "what do used forklifts actually fetch at auction" or to comp an asset before bidding. Filter by keyword (title match), asset_type, state and segment. Returns count, min/median/average/max final price, and recent examples. Only lots that closed with a recorded sale price above zero are counted, a closed lot that drew no bids is not a comp.

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": {
      "limit": 10,
      "keyword": "forklift"
    },
    "name": "us_auctions_sold_comps"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax example lots to return (1-50, default 10).
stateNo2-letter state code.
keywordNoFree-text title match, e.g. "forklift", "f-150", "cnc lathe".
segmentNogovernment | commercial. Commercial and government prices differ materially for the same asset, split them when it matters.
asset_typeNoOne of: vehicle | equipment | realestate | electronics | other.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / segment / description
      Previous value: -"government | commercial. Commercial and government prices differ materially for the same asset — split them when it matters."New value: +"government | commercial. Commercial and government prices differ materially for the same asset, split them when it matters."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely useful semantics beyond that: coverage spans commercial and government segments, only lots with a recorded sale price above zero are counted, and the result shape includes aggregates plus examples. It says nothing about history depth, recency window, rate limits, or auth, leaving real behavioral gaps.

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-loaded with the core definition, then usage, filters, return shape, and the comp-counting caveat in a logical order; every sentence carries information. The "no upstream site keeps but Pipeworx retains" aside is mildly promotional but does convey market coverage.

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?

A read-only, zero-required-param query tool with no output schema, and the description covers input filters and the returned aggregates (count, min/median/average/max, examples). The main omission is the time span of the historical data, which matters for comps but is not stated anywhere.

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 schema already explains limit range/default, state code, keyword matching, segment values, and asset_type values. The description only restates the filter set (keyword title match, asset_type, state, segment) without adding syntax or interaction details, so the schema does the heavy lifting.

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 precise resource (historical SOLD prices / final hammer price of closed lots) with a clear verb-like scope, and explicitly separates itself from the closing-soon/upcoming side of the auction tools by emphasizing closed lots. The note that only sold lots count further pins down what the tool actually returns.

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 two concrete usage scenarios ("what do used forklifts actually fetch at auction", comping before bidding) and an exclusion rule: a closed lot with no bids is not a comp. It does not name a sibling alternative such as us_auctions_search for open listings, so it stops short of explicit routing.

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.