Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_properties_zpid_price_history

Transaction price history — $0.02 per call Origin: https://re-data-refinery.ares-hms.workers.dev. Price: $0.02 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_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
zpidYesZillow property id
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.9/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 the two things an agent could not otherwise know: the call costs $0.02 and settlement runs through x402 (USDC on Base) against a specific origin. It says nothing about what a record contains, whether results are paginated, or what happens on a failed payment beyond the challenge flow implied by the schema.

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 description is short but wastes its budget: '$0.02 per call' is stated twice and the pricing/origin details crowd out any statement of usage or return content. The identification of the tool is buried mid-string rather than front-loaded.

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 is the only place an agent could learn what price-history records look like, how far back they go, or how they are ordered – and it covers none of that. For a paid call, the absence of any expectation-setting about the response is a real gap.

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% and both parameters are self-explanatory in the schema, including the x402_payment header semantics. The description adds no additional meaning about zpid format or payment reuse, so the baseline 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?

The description names a specific resource – transaction price history – which is enough to distinguish it from siblings like refinery_properties_zpid_tax_history or refinery_properties_zpid_schools. It lacks an explicit verb ('retrieve'), but the resource and the zpid parameter make the intent unmistakable.

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 guidance on when to use this tool versus the tax_history or general property siblings, and no stated preconditions beyond the payment mention. An agent must infer from the name alone that this is the price-history variant.

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.