Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_search

Scored property search by location — $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": {
      "q": "<q>"
    },
    "name": "refinery_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCity/state or ZIP, e.g. "Columbus OH" or "43215"
limitNoMax results 1-40
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 behavioral facts: the $0.05 cost and the x402/USDC-on-Base payment rails plus the origin. It omits rate limits, what a 'scored' result contains, whether payment is mandatory on first call, and any failure modes, which matters for a paid 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 short and front-loads the purpose, but the price appears twice ('$0.05 per call' in the lead and again in the pricing clause) and the 'Origin:' URL is jammed in without a separator, making it read like pasted metadata rather than prose.

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, yet the description never describes what a result looks like, what 'scored' fields are returned, or whether the first call returns only a 402 challenge. For a paid search tool an agent needs that to plan the call sequence, and it is absent.

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 the q/limit/x402_payment descriptions already explain format and the challenge flow, so a baseline 3 applies. The description adds no parameter-level meaning (e.g., what scoring inputs are, whether limit affects cost) beyond the schema.

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 description states a verb and resource ('Scored property search') and adds a scope qualifier ('by location'), so the basic purpose is legible. However, it never distinguishes this from the sibling 'refinery_properties' or explains what 'scored' means, so an agent can't tell which property lookup to choose without opening the schemas.

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 or when-not-to-use guidance and no named alternative. The only conditional information is the implicit pay-per-call model, which tells the agent nothing about when this search is preferable to refinery_properties or the zpid-specific lookups.

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.