Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_cash_buyers

Cash-buyer intelligence — $0.50 (zip rollup) / $2.50 (parcel evidence) per call Origin: https://re-data-refinery.ares-hms.workers.dev. Price: $0.50 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_cash_buyers"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit ZIP (e.g. 43211) — buyer rollup, $0.50
limitNoTop buyers returned for ZIP queries (default 10, cap 50)
parcelNoFranklin County parcel digits, e.g. 01000051500 — deed evidence, $2.50
min_scoreNoBuyer score floor 0-100
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

C2.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose something genuinely important: every call is paid, via x402 USDC-on-Base, with different prices per mode. It omits equally important behavior — that a first call without x402_payment returns a Payment Required challenge, whether zip and parcel can be combined, and what a 'rollup' or 'deed evidence' payload actually contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The text is short but sloppily structured: 'Origin: https://...' is glued onto the first sentence without punctuation and the $0.50 figure is stated twice while the $2.50 parcel price is only mentioned once. Pricing dominates the limited space rather than the tool's function.

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

Completeness2/5

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

For a five-parameter, no-output-schema, no-annotation data tool, the description should say what comes back from each mode and how the payment flow resolves. It covers the payment model but leaves the returned data entirely undescribed while there is no output schema to fall back on.

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%, so the schema already defines all five parameters, including the x402_payment handshake. The description only reinforces the cost mapping between the zip ($0.50) and parcel ($2.50) parameters, adding marginal meaning beyond the schema.

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

Purpose3/5

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

'Cash-buyer intelligence' names the resource but not the operation — it never says it returns or lists buyers. The two modes (zip rollup vs. parcel evidence) are useful differentiation, but most of the sentence is spent on pricing rather than purpose, and no sibling tool is contrasted.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives among the many refinery_* siblings. The price split lets an agent infer that ZIP is the cheap bulk mode and parcel is the expensive single-record mode, but that is an inference, not stated guidance.

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.