Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_preforeclosures

Pre-foreclosure leads across 19 Ohio counties — $0.05 per call Origin: https://re-data-refinery.ares-hms.workers.dev. Price: $0.05 per call via x402 (USDC on Base).

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": "refinery_preforeclosures"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit ZIP filter
cityNoCity filter
limitNoMax records (default 50, cap 200)
countyNoOhio county, e.g. Cuyahoga
min_emvNoEstimated market value floor (USD)
with_valueNo"1" returns only records with an estimated value
x402_paymentNoOptional. X-PAYMENT header value an x402 client produced after settling this exact origin+params challenge. Omit to first receive the Payment Required challenge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose genuinely useful context: per-call cost of $0.05 and the x402 USDC-on-Base payment flow. It says nothing about rate limits, whether the 19-county scope can be widened, result pagination, or what a failed payment returns.

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?

It is short and front-loads the resource scope, but the price is stated twice in one line and a bare origin URL is wedged between the two price mentions, creating noise rather than structure.

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

Completeness3/5

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

Coverage of cost and the x402 handshake is helpful for a paid, unannotated, output-schema-less tool with seven optional filters. However, nothing explains the shape or ordering of returned lead records, and the relationship to the similarly named foreclosure tool is left unresolved.

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%, including a clear explanation of x402_payment and the limit cap of 200, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond what is already documented, which is the correct baseline here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (pre-foreclosure leads) and a bounded geographic scope (19 Ohio counties), which is enough to know what comes back. It omits an explicit verb and never distinguishes itself from the near-identically named sibling 'refinery_foreclosures', so an agent must guess how the two differ.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of the obvious alternative 'refinery_foreclosures'. The only situational information is the payment path, which is about how to call it, not when.

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.