Skip to main content
Glama

DFX Real Estate Intelligence

by io.github.Capital-W-Holdings
OverviewDiscussionsAdmin

Confirmed commercial mortgage maturities for one state

debt_maturity_schedule
Read-onlyIdempotent

Free, keyless and unauthenticated. Returns the LOAN rather than the event: for one US state and one forward window, up to 200 loans with maturity date, original and current principal, interest rate, 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,821 of 19,821 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. Every response states how many loans DFX holds for the filter and whether the delivery is complete, so an answer capped at 200 rows is never presented as the whole population. Each row says whether a maturity event was published for the loan. A missing event does not mean the loan is defeased: loans filed as defeased (ABS-EE code F, or IP for a portion) are withheld, and code X means defeasance is not allowable, so an X loan must refinance or pay off at maturity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum loans, up to 200.
stateYesTwo letter state code. Required.
within_daysNoForward window from today. Default 548, eighteen months.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / authorize
      Removed value: -{
-  "description": "Omit to be quoted. Supply to be charged and served in one response.",
-  "properties": {
-    "max_price_usd": {
-      "description": "YOUR ceiling, checked before ours. If the price exceeds it you are refused rather than charged.",
-      "type": "number"
-    },
-    "quote_id": {
-      "description": "from the PAYMENT_REQUIRED reply",
-      "type": "string"
-    }
-  },
-  "required": [
-    "quote_id",
-    "max_price_usd"
-  ],
-  "type": "object"
-}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum loans, up to 200. The price does not change with the row count."New value: +"Maximum loans, up to 200."
    • changedInput schema / properties / state / description
      Previous value: -"Two letter state code. Required: the schedule is priced per state."New value: +"Two letter state code. Required."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say read-only/non-destructive/idempotent. The description adds a large amount of valuable behavioral context: free keyless access, loan-level deduplication, ordering by maturity, confirmed maturity basis (19,821/19,821 from SEC/HUD filings), delivery-completeness reporting, and a principled treatment of defeasance codes (F, IP, X) and withheld loans. This far exceeds the annotation bar.

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?

The paragraph is long, but each clause carries unique information such as authentication, dedup, data quality, completeness, and defeasance code interpretations. The access and 'loan rather than event' statement are front-loaded. It could be tightened slightly, but it is not bloated.

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

Completeness5/5

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

Because no output schema exists, the description compensates by enumerating all the return fields (maturity date, principals, rate, lender, instrument, origination date, address), ordering/scoping, completeness reporting, and defeasance edge cases. An agent has everything needed to call the tool correctly and interpret results.

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 the state, limit, and within_days parameters are already documented. The description echoes 'one state', 'one forward window', and 'up to 200 loans,' but does not add new semantic meaning beyond what the schema already provides. 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?

The description uses a specific verb ('Returns'), a well-defined resource ('LOAN'), and exact scoping ('one US state and one forward window'), while explicitly distinguishing itself from the event-level tools. The mention of maturity, principal, lender, and secured property makes the tool concrete. It clearly is not a generic search or event tool.

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?

The description gives explicit context: it is for one-state, one-forward-window loan-level maturity data, is keyless/unauthenticated, and returns loans rather than events. It stops short of naming sibling tools or stating specific when-not-to-use conditions, but the core usage scenario is clearly inferable.

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

All DFX Real Estate Intelligence toolsInspect
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