Skip to main content
Glama

Bigiron Sold Search

bigiron_sold_search
Read-onlyIdempotent

Search CONFIRMED-SOLD equipment lots on bigiron.com for comps, title, make/model/year, quantity, seller, location and close date for lots that actually sold. IMPORTANT: bigiron.com does not expose the realized hammer price in this page shape (verified: 0/100 sampled sold lots carry a nonzero price field, even with 60+ bids), final_price is always null with an explanatory note; num_bids is the closest available demand signal. Use bigiron_search for current asking prices instead. Sourced from bigiron.com/Search?filter=Sold.

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": 3,
      "query": "tires"
    },
    "name": "bigiron_sold_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, starting at 1 (each page holds up to 20 lots)
limitNoMax lots to return, 1-20 (default 20)
queryYesSearch keywords, e.g. "planter", "grain trailer", "combine tires"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), but the description adds something no structured field could: final_price is always null because bigiron.com does not expose the realized hammer price. It backs this up with evidence (0/100 sampled sold lots, even with 60+ bids) and points to num_bids as the best demand signal. That directly prevents the agent from misusing a comps tool.

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?

The description is front-loaded with purpose, then the critical price caveat, then the routing alternative. The verification evidence ('0/100 sampled sold lots... 60+ bids') is slightly verbose, but it earns its place by making the limitation credible. A few words could be trimmed without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description has to carry the burden of explaining return behavior. It does exactly that: it lists the result fields, explains that final_price is always null and why, and redirects the agent to num_bids. Nothing needed to use a read-only, open-world search tool correctly is missing.

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%: page, limit, and query are all documented in the schema with page size and defaults. The description adds no parameter-level meaning such as query syntax, stemming, or multi-word behavior beyond what the schema already provides. A 3 is appropriate because the schema already 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 specific verb and resource ('Search CONFIRMED-SOLD equipment lots on bigiron.com') and enumerates the returned fields: title, make/model/year, quantity, seller, location, close date. It also explicitly contrasts itself with bigiron_search, which serves current asking prices, so an agent can pick between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the use case (comps for lots that actually sold) and names the alternative and the condition that selects it: 'Use bigiron_search for current asking prices instead.' The main caveat is the price limitation; it flags this up front.

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.