DFX Real Estate Intelligence
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_addressA | Turn a street address into canonical DFX object ids, with the match basis and any ambiguity stated. Returns typed objects: a 'property' (national federal programme multifamily) and/or a 'parcel' (Massachusetts assessor and registry layer). These are separate populations that barely overlap, so an address may return one, the other, or both. Free. Start here, then call get_property_record with an id. |
| resolve_organizationA | Turn an owner, manager, lender or servicer name into canonical DFX entity ids. A name is treated as a blocking key and never as an identity, so all candidates are returned rather than a guess. Free. Person lookup is deliberately not offered. |
| get_property_recordA | Given a DFX id from resolve_address, return current state, dated events, ownership and management relationships, debt with maturity dates and maturity basis, recorded sales with consideration plus registry book and page, and the provenance of each. Sales carry BOTH the instrument total and this parcel's allocated share, because a deed repeats its full price on every parcel it covers. Free. |
| search_property_eventsA | Dated events over US properties and parcels, with provenance and a headline you can show a person. Covers LIHTC compliance period endings (the Year 15 recapitalisation trigger, 11,956 of them), HUD subsidy contract expiries (4,721), scheduled loan maturities (3,422) now national rather than Massachusetts, CMBS distress and workout reporting (167 delinquency flags across 26 states, 128 foreclosures across 22), issued building permits and demolition filings (Boston only), and recorded sales (43,680, 2 states). 8,194 events fall inside the next 548 days, measured 2026-09-09. Filter by event type, state and days ahead. An unrecognised event type is REFUSED with the served vocabulary, never answered with an empty list. Free. PAGING: a full page carries |
| search_parcelsA | Search the assessor parcel layer with filters instead of one exact address. Filter by state, municipality, assessor land use code, owner-occupancy, tax-exempt status, year built and assessed value range; results carry assessed value, gross building area, assessed value per square foot, the annual tax and the year built. This is the only way to ask a QUESTION of the parcel layer: resolve_address needs an address you already have. Every answer states the true match count alongside the sample, and a search that matches nothing names the filter that emptied it rather than returning a bare empty list. At least one filter is required. Free. |
| what_can_dfx_answerA | Describe an objective in natural language and get back whether DFX can help, which tool to call, the arguments to call it with, and a free sample of the result. Says no clearly when the answer is no, and records what was asked so unmet demand shapes what DFX builds next. Call this first if you do not know what to ask for. |
| changes_sinceA | Poll for what is NEW to you, ordered by when DFX learned it rather than by when it happened. TWO CALLS ARE REQUIRED BEFORE YOU SEE ANYTHING: the first, with no cursor, deliberately returns ZERO events and a starting position; the second, with that cursor, returns what DFX learned in between. If you want rows now rather than a subscription, call search_property_events instead. Filter by event type, state, or a specific property or parcel id. Deterministic and indexed, so it is cheap to call often. Free.
HISTORICAL FAMILIES DO FLOW THROUGH HERE. |
| debt_maturity_scheduleA | PAID: $1.00 USD per delivered schedule. This is the ONLY priced tool on this server. The other eleven are free, keyless and permanently so.
Returns the LOAN rather than the event: for one US state and one forward window, up to 200 loans with maturity date, original principal, lender name, instrument type, origination date and the secured property's address, deduplicated to one row per loan and ordered by maturity.
Every maturity_basis is 'confirmed': 19,881 of 19,881 loans carry a date filed with the SEC by a servicer or recorded by HUD, and none is estimated or inferred from a term length.
HOW TO GET A PRICE, FREE: call this tool with no |
| open_dfx_accountA | Creates an economic identity you control, with NO money in it. Free. No human approval, no email, no contract, no sales call. It returns an account key ONCE. DFX stores only its digest and can never show it to you again, so store it before your next call. THE ACCOUNT STARTS AT $0.00 AND CANNOT BUY ANYTHING. DFX mints identity and never credit: a balance moves only when Stripe confirms a payment and DFX re-reads that payment from Stripe. There is no argument anywhere on this server through which you can propose a balance. Call this only if you intend to buy a paid capability. Every discovery, coverage, resolution, property record and event search tool on this server is free, unauthenticated and does not need an account, permanently. |
| fund_dfx_accountA | Opens a Stripe payment for exactly one quote, into the account key you present, and returns the hosted payment URL and a payment id. THE AMOUNT IS READ FROM THE QUOTE, SERVER SIDE. There is no field on this tool through which a price can be proposed, raised or lowered. A CARD MUST STILL BE AUTHORIZED. That is the card network's boundary and not a DFX design choice: show the URL and the price to your human, or present your own payment credential to Stripe. Everything either side of that step is callable by a machine. Returning to the success page is NOT a receipt. Poll dfx_payment_status until it reports PAID; that reads the DFX ledger, which advances only on a Stripe event DFX verified and re-read from Stripe. This build collects Stripe TEST payments only. No real money moves. |
| dfx_payment_statusA | Reads the DFX payment ledger for one quote. Free.
It is the ONLY trustworthy answer to 'did my payment go through'. A browser redirect, a Stripe success page and a client's own belief are all not receipts. This reads DFX rows, which advance only on a Stripe event DFX verified against Stripe's signature and then re-read from api.stripe.com.
AWAITING_PAYMENT means keep polling. PAID means your balance is funded and you may now repeat the paid call with |
| dfx_coverageA | Measured coverage, served sources, object types and the known gaps stated plainly, including where geography is a single state and where nothing carries a calibrated probability. Call this before concluding that an empty result means an absent market.
Call it with NO arguments for the full grid: every event family, every state, measured. Call it with |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes, and the descriptions explicitly separate similar ones such as search_property_events versus changes_since and the paid debt_maturity_schedule versus the free event search. A few pairs could still be confused at a glance, but the documentation resolves the ambiguity well.
The API uses snake_case throughout, but naming styles are mixed: some tools follow verb_noun (resolve_address, search_parcels, open_dfx_account), while others are noun phrases or questions (changes_since, debt_maturity_schedule, dfx_payment_status, what_can_dfx_answer). The inconsistency is noticeable but not chaotic.
Twelve tools is within a reasonable range for a server that combines real estate data discovery with an account and payment flow. The count feels justified rather than padded, though the billing-related tools add some surface area beyond the core domain.
The tool set covers address and organization resolution, property records, event search, parcel search, coverage, change polling, and a full paid-capability flow. It is solid for a read-focused real estate intelligence API, though a direct parcel-by-ID retrieval endpoint is not clearly present and would round out the surface.