Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_properties

City-filtered scored property list — $0.03 per call Origin: https://re-data-refinery.ares-hms.workers.dev. Price: $0.03 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_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOhio city, e.g. Columbus (18 supported cities)
liveNo"0" forces the cache instead of a live RealtyAPI search
max_priceNoUSD price ceiling
min_priceNoUSD price floor
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.7/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 it does disclose two genuinely useful behaviors: a $0.03 per-call cost and that payment settles via x402/USDC on Base, plus the origin host. It omits other material behavior — what "scored" means, default cache-vs-live behavior, retry/charge semantics on failure, and any rate limits — so it is partially but not fully transparent for a paid mutation-of-state (billing) 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?

The definition is short, but it is not front-loaded well: the pricing claim appears twice in two different phrasings, and the origin URL is wedged mid-sentence between them. Deduplicating the price and leading with what the tool returns would make every sentence earn its place.

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 paid data tool with no annotations and no output schema, the description should explain what a "scored" property record contains and how billing interacts with repeated calls. Neither is covered, and the undefined scoring concept is the single most important unknown an agent faces before calling.

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 every parameter including city, live, price bounds, and x402_payment is already documented in the schema; baseline 3 applies. The description adds no parameter-level meaning beyond restating the city filter, and does not explain the two-step challenge-then-pay sequence that x402_payment implies.

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?

"City-filtered scored property list" names a resource (property list), a filter (city), and an ordering qualifier (scored), so an agent can tell it is a bulk list rather than the zpid detail siblings. However, "scored" is never defined, and the sentence is buried under pricing boilerplate, so the actual purpose reads as a fragment rather than a clear statement of what the tool returns.

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 guidance, no when-not-to-use, and no explicit routing to alternatives such as the refinery_properties_zpid family or refinery_search. The only hint is the word "list" and the city filter, leaving the agent to infer that this is the entry point for city-level browsing.

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.