SiteCheck Company Records

Live US government surplus auctions on GovDeals

gov_govdeals

Read-only

Live US government surplus auctions on GovDeals for a keyword: asset ID, title, make, model, model year, category, current bid (USD), reserve-not-met flag, auction start and end (UTC and as shown), time remaining, seller agency, city, state and ZIP, photo and asset URL; plus the total number of matching auctions. Sort by relevance, ending soonest, newest or bid. Related tools on this server, for a different need: gov_data_gov_uk when you need UK government open datasets from the data.gov.uk catalogue; gov_governmentbids when you need open US/Canadian government bid solicitations listed. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "gov_govdeals"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Keyword, e.g. truck, forklift, laptop (required)
`page`	No	Page number from 1 (default 1)
`sort`	No	relevance (default), ending, newest, price_high or price_low
`limit`	No	Results per page, 1 to 100 (default 24)

Output Schema

Name	Required	Description	Default
`q`	No
`page`	No
`sort`	No
`count`	No
`items`	No
`total`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only and open-world safety. The description adds genuinely new behavior: cost of $0.002 USDC per successful call via x402 on Base/Solana/Arc, and that failed calls are not charged — key for an agent deciding whether to spend. It does not discuss pagination limits or rate limits, so not 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and free of filler, but it is one long semicolon-chained sentence, and the exhaustive field enumeration largely duplicates what the output schema already provides. The pricing and related-tool sentences earn their place; the field dump does not.

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?

Covers purpose, result contents, sorting, alternatives, and payment model, which is enough to invoke it correctly given a full output schema and annotations. The only gaps are pagination behavior and the sort-value mismatch with the schema.

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%, so the schema already documents q, page, sort and limit; the description adds little beyond restating them. Worse, its sort list ('relevance, ending soonest, newest or bid') diverges from the schema's actual values ('relevance, ending, newest, price_high or price_low'), offering no clarifying guidance.

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/resource ('Live US government surplus auctions on GovDeals for a keyword') and enumerates exactly what a result contains. An agent can distinguish it from gov_governmentbids (solicitations) and gov_data_gov_uk (datasets) from the text alone.

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?

Explicitly routes two alternatives by need: gov_data_gov_uk for UK open datasets and gov_governmentbids for open US/Canadian solicitations. No explicit 'when not to use' clause (e.g. non-surplus, non-US listings), which keeps it short of a 5.

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

All SiteCheck Company Records 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.

Resources

Need Help?