Skip to main content
Glama
Sign In

DFX 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. Narrow the state to one county (county) or to a metro's counties (metro, a CBSA code or name such as 'Dallas-Fort Worth-Arlington'); a county or metro answer also counts the loans in the state whose property carries no county. A CMBS lender is the originator code as filed (SG, WFB) with the parent lender's name beside it (Societe Generale, Wells Fargo). Every maturity_basis is 'confirmed': 25,412 of 25,412 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

NameRequiredDescriptionDefault
limitNoMaximum loans, up to 200.
metroNoOptional. A metro (OMB core based statistical area) as a five digit CBSA code ('19100') or a name ('Dallas-Fort Worth-Arlington', 'Boston'): the metro's counties inside `state`. A metro crossing a state line is served one state per call and the answer names the other states. An unknown or ambiguous name is refused with the candidates.
stateYesTwo letter state code. Required.
countyNoOptional. One county in `state`, by name: 'Dallas' or 'Dallas County'. Matches the secured property's county as filed.
within_daysNoForward window from today. Default 548, eighteen months.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / county
      Added value: +{
+  "description": "Optional. One county in `state`, by name: 'Dallas' or 'Dallas County'. Matches the secured property's county as filed.",
+  "type": "string"
+}
    • addedInput schema / properties / metro
      Added value: +{
+  "description": "Optional. A metro (OMB core based statistical area) as a five digit CBSA code ('19100') or a name ('Dallas-Fort Worth-Arlington', 'Boston'): the metro's counties inside `state`. A metro crossing a state line is served one state per call and the answer names the other states. An unknown or ambiguous name is refused with the candidates.",
+  "type": "string"
+}
  2. 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."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile, yet the description adds substantial operational context: free/keyless/unauthenticated, one row per loan deduplicated, ordered by maturity, hard 200-row cap with population counts so a capped answer is never mistaken for the full set. It also discloses a non-obvious exclusion — defeased loans (ABS-EE F/IP) are withheld and code X means defeasance is not allowable, so silence about an event does not imply defeasance.

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?

Dense and mostly front-loaded — the row shape and scoping arrive before the evidentiary detail. It runs long across several paragraphs, and the closing defeasance digression, while useful, is the least essential block relative to what an agent needs to issue the call.

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?

There is no output schema, so the description carries the full return-value burden and does: field list, dedup, ordering, row cap, population counts, per-row event flag, and the meaning of missing events. An agent has everything needed to call it and interpret the result correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline would be 3, but the description adds real semantics: county/metro answers also count in-state loans whose property carries no county, metro is a CBSA code or name, and every maturity_basis is confirmed with the 25,412/25,412 SEC-or-HUD sourcing. It doesn't elaborate on limit or within_days beyond the schema, keeping it at a 4 rather than 5.

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 and resource plus the exact row shape: '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...'. The 'loan rather than the event' framing lets an agent distinguish this from event-oriented siblings without consulting schemas.

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?

Gives concrete scoping guidance: narrow to a county or a metro (CBSA code or name), one state per call, and what happens when a name is ambiguous ('refused with the candidates'). It establishes context clearly but never names a competing sibling (e.g. search_cmbs_loans or search_credit_maturities) or states when NOT to use this tool.

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

All DFX 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