Skip to main content
Glama

Bigiron Search

bigiron_search
Read-onlyIdempotent

Search active US ag/construction/livestock/transportation equipment auctions on bigiron.com, a national online timed-auction platform. Returns live listings with current bid, Buy-It-Now asking price (if offered, NOT a sold price), make/model/year, seller, location and auction close time. Bids are served through a 5-minute result cache, so the current bid can be up to five minutes old: near the close of an auction treat it as a lower bound, never as the final price. Sourced from bigiron.com/Search.

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": "tractor"
    },
    "name": "bigiron_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, starting at 1 (each page holds 20 lots)
limitNoMax lots to return, 1-20 (default 20)
queryYesSearch keywords, e.g. "tractor", "skid steer", "Angus bred heifers"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds genuinely non-obvious behavior: a 5-minute result cache, the caveat that current bid may be stale and should be treated as a lower bound near close, and that Buy-It-Now is an asking price, not a sold price. It does not cover pagination limits or rate limits, keeping it short of a 5.

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 dense sentences, front-loaded with what is searched and where, then return contents, then the staleness caveat. No filler and no repetition of the schema.

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?

With no output schema, the description carries the return-value burden and does so: it enumerates current bid, Buy-It-Now, make/model/year, seller, location and close time, and flags the cache caveat. Nothing an agent needs to call or interpret results 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 coverage is 100% and all three parameters (query, page, limit) are documented in the schema with examples and ranges. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 (Search) and resource (active US ag/construction/livestock/transportation equipment auctions) with the source domain, and the word 'active' plus 'live listings' implicitly separates it from the sold-listings sibling. An agent can tell what this returns without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by 'active' auctions and 'live listings', which suggests sold-price lookups belong elsewhere, but no alternative tool is named and there is no explicit when-not guidance. The agent must infer the boundary with bigiron_sold_search.

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.