Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_tax_sales

Scored county tax-sale 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

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": {
      "city": "<city>"
    },
    "name": "refinery_tax_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesOhio city, e.g. Columbus
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.8/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 and does disclose genuinely useful behavior: the tool is paywalled at $0.05 per call via x402 (USDC on Base) and tied to a specific origin. It does not reveal what 'scored' means, whether results are paginated or cached, or what a successful response contains — notable gaps for an unannotated tool.

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 brief, but the pricing information is duplicated ("$0.05 per call" appears twice) and the 'Origin:' fragment is glued onto the sentence without structure or punctuation. Front-loading the resource name is good; the leftover text is wasted.

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 two-parameter tool with no output schema, the description is barely sufficient: it covers cost, origin, and payment mechanism, but omits what a 'lead' object looks like and whether the tool is Ohio-only despite the schema hint. Adequate but with clear gaps.

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 both parameters (city, x402_payment) are already documented, including the payment-challenge flow. The description adds no extra semantics about the city input or the payment header beyond repeating the price, so the baseline 3 applies.

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?

The phrase "Scored county tax-sale leads" names a specific data resource and implicitly separates it from siblings such as refinery_auctions or refinery_foreclosures, but there is no verb and no statement of what the call actually returns or how leads are 'scored', leaving the action ambiguous.

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?

Nothing says when to pick this over refinery_auctions, refinery_foreclosures, or refinery_properties. The only usage-adjacent information is price and payment mechanics, not task selection guidance or exclusions.

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.