SiteCheck Jobs & Property

Upcoming U.S. Treasury auctions of seized/forfeited real

realestate_auction_com_property_scraper_ppe

Read-only

Upcoming U.S. Treasury auctions of seized/forfeited real property (official treasury.gov list): property type, address, state, ZIP, sale method (online auction or broker sale), auction date (null while 'coming soon'), Treasury sale number, short description (size, rooms, lot) and detail-page URL. Filter by state or property type. Replaces Auction.com, which blocks automated access. Usually answers in about 7 s, up to 15 s on slower calls; allow a 30 s timeout. Related tools on this server, for a different need: realestate_auction_com_property when you need HUD homes for sale by online bid in a US state or city; realestate_zillow_rentals_scraper_ppe when you need typical market rent for a US ZIP code from the Zillow. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "realestate_auction_com_property_scraper_ppe"
  }
}

Input Schema

Name	Required	Description	Default
`type`	No	Optional words of the property type, e.g. single family, commercial, land
`state`	No	Optional 2-letter US state code, e.g. TX

Output Schema

Name	Required	Description	Default
`count`	No
`total`	No
`source`	No
`checkedAt`	No
`properties`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only cover readOnly and openWorld; the description adds substantial context beyond them: typical ~7 s latency with a 30 s timeout recommendation, per-call pricing ($0.002 USDC via x402 on Base/Solana/Arc) with failed calls uncharged, and the data quirk that auction_date is null while a sale is 'coming soon'. Those are exactly the operational facts an agent needs before invoking.

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 resource and field list, then filtering, then latency, then alternatives, then price. Dense but nearly every clause carries information; the field enumeration partially duplicates the output schema and could be trimmed.

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?

An output schema exists, so return values needn't be spelled out, yet the description is complete on sourcing, latency, cost, and the null-date edge case. The one gap is whether the result set is paginated or capped, which an agent might reasonably want to know.

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% with two optional, self-documented params (type, state), so the schema already carries the semantics. The description's 'filter by state or property type' only restates that and adds no format or matching nuance beyond the schema.

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 resource (upcoming U.S. Treasury auctions of seized/forfeited real property from the official treasury.gov list) and enumerates the returned fields, so an agent knows exactly what data it gets. It also distinguishes itself from the named sibling by noting it replaces Auction.com, which blocks automated access.

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 the agent to alternatives with conditions: realestate_auction_com_property for HUD homes by online bid, realestate_zillow_rentals_scraper_ppe for market rent by ZIP. It also states the filtering dimension (state or property type). It lacks an explicit 'do not use this for' statement, but the routing guidance is clear.

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

All SiteCheck Jobs & Property 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?