Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_properties_zpid

Full scored detail for one property — $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

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": {
      "zpid": "<zpid>"
    },
    "name": "refinery_properties_zpid"
  }
}

Input Schema

NameRequiredDescriptionDefault
zpidYesZillow property id (returned as zpid by /search and /properties)
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 disclosure burden, and it does add real behavioral context: the call costs $0.03, is billed through x402 (USDC on Base), and originates from a specific worker URL. However it says nothing about what happens on a 402 challenge, whether calls are cached/idempotent, or what the returned 'scored detail' contains.

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 purpose, but the price is stated twice ('$0.03 per call' in the opening clause and again in 'Price: $0.03 per call via x402'), and the origin URL is jammed into the same sentence without structure.

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?

There is no output schema and no annotations, so the description should explain what the returned detail includes and how a failed/unpaid call behaves; instead it spends its budget on pricing and omits return shape entirely, leaving an agent unable to anticipate the payload.

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 both parameters (zpid and x402_payment) are already documented in the schema, including how to obtain the payment header. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the work.

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?

It states a resource (one property's detail, keyed by zpid) and implies full-record scope versus the narrower sibling endpoints (price_history, schools, tax_history), but 'full scored detail' never says what 'scored' means or what fields come back, so the purpose is only loosely pinned down.

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?

No when-to-use guidance at all: nothing tells the agent whether to call this instead of the sub-resource siblings (price_history, schools, tax_history) or when the cheaper per-topic endpoints suffice. The payment note implies a cost trade-off but never frames it as usage 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.