Gov Auctions

Auctions Search

auctions_search

Read-onlyIdempotent

Search live US government auction lots for physical assets sold to the public — surplus vehicles, heavy equipment, real estate, electronics — from state/local governments (GovDeals, AllSurplus) and IRS seized/forfeited property. Filter by free-text keyword (matched on the item title, e.g. "truck", "excavator", "pickup"), 2-letter state, asset_type (vehicle|equipment|realestate|electronics|other), max_price (current bid ceiling), and closing_within_hours. Returns each lot with source, title, location, current bid, close time, and a link. For historical sold prices use auctions_sold_comps instead.

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": {
      "state": "TX",
      "keyword": "pickup truck",
      "max_price": 5000,
      "asset_type": "vehicle"
    },
    "name": "auctions_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max lots (1-100, default 25).
`state`	No	2-letter state code of the item location, e.g. "TX", "CA".
`source`	No	Restrict to one source: govdeals \| allsurplus \| irs.
`keyword`	No	Free-text matched (case-insensitive) against the lot title, e.g. "truck", "forklift", "generator".
`max_price`	No	Only lots whose current bid is at or below this.
`asset_type`	No	One of: vehicle \| equipment \| realestate \| electronics \| other.
`closing_within_hours`	No	Only lots closing within this many hours from now.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 29, 2026

addedInput schema / examples

Added value: +[
+  {
+    "asset_type": "vehicle",
+    "keyword": "pickup truck",
+    "max_price": 5000,
+    "state": "TX"
+  },
+  {
+    "asset_type": "equipment",
+    "closing_within_hours": 24,
+    "keyword": "excavator",
+    "limit": 10
+  }
+]

First observedJul 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds context about the return fields (source, title, location, current bid, close time, link), which is helpful beyond the annotations.

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?

The description is two sentences, each earning its place. It front-loads the purpose, then details filtering and return info, and ends with a sibling hint. No unnecessary words.

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?

Given the tool's complexity (7 parameters, no output schema), the description covers all essential aspects: what it does, what it returns, and how to filter. It's sufficient for an agent to select and invoke the tool correctly.

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 coverage is 100%, so baseline is 3. The description adds value by explaining that 'keyword' is matched on the item title, 'state' is a 2-letter code, 'asset_type' enumerates values, and 'closing_within_hours' filters by time. This goes beyond the schema descriptions.

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 clearly states it searches live US government auction lots for physical assets, specifies the types of assets and sources, and distinguishes itself from the sibling tool 'auctions_sold_comps' for historical prices.

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 description provides explicit guidance on when to use this tool (search live auctions) and when to use alternatives ('auctions_sold_comps' for historical prices). It could further mention not to use for specific lot details (use 'auction_lot_details'), but the main distinction is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gov Auctions tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.