Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_properties_zpid_tax_history

Tax assessment 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_tax_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 does carry real behavioral weight by disclosing that the call is metered at $0.02 and settled via x402/USDC on Base, plus the origin URL — information an agent cannot get from structured fields. However, it says nothing about what the endpoint returns (years of assessments, fields, record counts) or whether the paid call is idempotent/retry-safe.

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 price '$0.02 per call' is stated twice in a three-sentence blurb, and the origin URL is jammed mid-sentence after an em dash with no punctuation separation, making it read as a malformed fragment. The content that remains is short but noticeably redundant and poorly ordered.

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?

This is a paid data-retrieval endpoint with no output schema and no annotations, so the description must carry the burden of explaining what comes back — and it does not. Payment mechanics are covered by the schema, but cost, retry/idempotency behavior, and result content are largely unexplained.

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 schema itself fully documents both zpid and the optional x402_payment handshake flow. The description contributes no additional parameter meaning, so the baseline of 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 phrase 'Tax assessment history' identifies a specific resource and implicitly distinguishes this tool from the sibling refinery_properties_zpid_price_history by dataset (tax assessments vs. sale prices). It lacks a verb and any notion of scope or return shape, which keeps it below a 5, but an agent can identify the resource unambiguously.

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 about when to pick this over price_history, schools, or the base property endpoint — the reader must infer it from the resource name alone. The only conditional instruction present is the payment handshake, which is a mechanics note rather than a use case.

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.