SiteCheck Jobs & Property

Official US mortgage application totals from the CFPB HMDA

realestate_hmda_mortgage_loan_data

Read-only

Official US mortgage application totals from the CFPB HMDA Data Browser API for one state and year: number of loans and their total dollar amount (aggregated, no borrower data). Filter by HMDA action taken (1 = loan originated, default). Related tools on this server, for a different need: realestate_bankrate_mortgage_rates when you need Today's US mortgage rates from Bankrate: national average. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "state": "<state>",
      "year": "<year>"
    },
    "name": "realestate_hmda_mortgage_loan_data"
  }
}

Input Schema

Name	Required	Description
`year`	Yes	Four-digit HMDA year, e.g. 2022
`state`	Yes	Two-letter US state code, e.g. WI
`actionTaken`	No	HMDA action taken code (default 1 = loan originated)

Output Schema

Name	Required	Description	Default
`year`	No
`state`	No
`source`	No
`checkedAt`	No
`loanCount`	No
`actionTaken`	No
`totalAmountUsd`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful context beyond them: results are aggregated with no borrower-level data, and the pricing model charges only successful calls at $0.002 in USDC across Base, Solana, or Arc.

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?

Core purpose is front-loaded in the first sentence, with the related-tool pointer and pricing following. The pricing sentence is long but materially useful to an agent deciding whether to call; nothing is purely redundant.

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

Completeness4/5

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

With an output schema present, return values need not be explained, and the description covers scope, filter semantics, aggregation guarantees, and cost. For a simple three-parameter aggregation tool, that is close to complete.

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%, with each parameter documented including the default value for actionTaken. The description repeats the actionTaken default (1 = loan originated) and notes the aggregation scope but adds no new syntax or format guidance beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: aggregated mortgage application totals (loan count and dollar amount) from the CFPB HMDA Data Browser API, scoped to one state and year. It also names the sibling it is not (realestate_bankrate_mortgage_rates) and the different need that sibling serves.

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

Usage Guidelines4/5

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

Explicitly frames the scope as one state and year with an optional actionTaken filter, and routes the agent to bankrate rates when the need is current rates rather than historical application totals. It stops short of stating exclusions or a full when-not-to-use list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Jobs & Property tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?