Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_auctions

Combined foreclosure + tax-sale + auction leads — $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_auctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit ZIP filter
cityNoOhio city filter
typeNoAuction type filter
statusNoFilter by status, e.g. active
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.3/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 burden. It does disclose the two most important behavioral traits — paid access at $0.05 per call and settlement via x402/USDC on Base — plus the origin URL. However it says nothing about result volume, pagination, or what a 'lead' record contains, leaving significant behavioral gaps for a paid data query.

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?

The description is short and front-loads the resource, which is good. But the price is stated twice ('$0.05 per call' appears in the opening clause and again at the end) and the 'Origin:'/'Price:' fragments are unpolished, so a sentence of content is spread across redundant phrasing.

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?

For a five-parameter, all-optional read query with full schema coverage and no output schema, the definition covers cost and payment mechanism but omits return shape, result limits, and any indication of what filters combine with what. It is adequate to invoke, but not complete for predicting output.

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 all five parameters including the x402_payment challenge flow are already documented in the schema. The description adds no syntax, valid values, or interaction guidance beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific resource with its scope: 'Combined foreclosure + tax-sale + auction leads'. The word 'combined' implies aggregation across the three lead types, which loosely distinguishes it from the separate refinery_foreclosures and refinery_tax_sales siblings, but it never names them or states the difference explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: 'combined' suggests this tool is the union alternative to the per-category siblings, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer selection criteria from the word 'combined' alone.

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.