Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_properties_zpid_schools

School ratings near one property — $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_schools"
  }
}

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

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations, so the description carries the full burden; it does disclose the paid x402 model (USDC on Base, $0.02 per call) and the origin, which is genuinely useful behavioral context. It still omits response shape, whether ratings are per-level or per-school, and any error or rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded with the purpose, which is good. The $0.02-per-call price is repeated twice (once inline, once after the origin URL), a small redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the description covers purpose and payment mechanics but leaves the agent guessing about the returned data. Adequate but with a clear gap on what 'school ratings' contains.

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%, so zpid and x402_payment are fully documented in the schema; the description only reinforces that the query targets one property. Baseline 3 applies since the schema does the heavy lifting.

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?

Description names the specific resource and scope: school ratings for a single property, keyed by zpid. That is enough to separate it from siblings like refinery_properties_zpid_price_history or refinery_properties_zpid_tax_history, though it doesn't explicitly say so.

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 versus the sibling property-detail tools or the broader refinery_search. The agent must infer that it is the per-property school-rating lookup from the name alone.

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.