Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_foreclosures

Scored active foreclosure leads by city — $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_foreclosures"
  }
}

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

B3.1/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 a genuinely important behavioral trait: this is a paid call at $0.05 via x402 (USDC on Base) against a specific origin, so the agent knows to expect a payment challenge. Beyond that it says nothing about what "scored" means, what fields come back, coverage limits, or whether repeated calls are billed again — significant gaps for a metered tool.

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 word count is low, but the text is a malformed run-on: "— $0.05 per call Origin: <url>. Price: $0.05 per call via x402 (USDC on Base)." states the price twice and jams origin and price together without structure. It is short without being efficient, and the single useful scope fact is not 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 are no annotations and no output schema, so the description is the only place an agent can learn what a returned lead looks like or what the score represents — and it supplies neither. For a paid, metered query tool with an unusual payment handshake, this leaves the agent unable to predict response shape or confirm the payment flow beyond what the schema hints.

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 city and x402_payment are already documented in structured fields, making 3 the baseline. The description only echoes "by city" and never mentions the x402_payment round-trip (challenge then settled header), so it adds no meaning beyond the schema.

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?

"Scored active foreclosure leads by city" names a specific verb (returns/scored leads), a specific resource (active foreclosure leads) and a scope constraint (by city). An agent can distinguish it from preforeclosure or tax-sale siblings by the word "foreclosure" plus "active". It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "by city" implies the tool is used for city-scoped lookups and the schema narrows this to Ohio cities, which is a reasonable implied usage condition. However, there is no explicit when-to-use, when-not-to-use, or pointer to refinery_preforeclosures for the pre-foreclosure stage, leaving the agent to infer the boundary.

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.