Skip to main content
Glama

CMBS loans with status, special servicing, DSCR, maturity and sponsor

search_cmbs_loans
Read-onlyIdempotent

Loans on the ACTIVE CMBS tape (SEC ABS-EE, each loan's latest monthly reading, read within 100 days of the newest period) with the servicer's own fields: payment status (current, 30/60/90 days, non performing matured balloon), special servicer and transfer date, whether it is in special servicing now, workout strategy, modification, current DSCR with its basis, occupancy, appraisal and LTV, balance, maturity, originator (the code as filed, e.g. 'WFB', with the parent lender's name beside it as lender_name), and the sponsor as the prospectus annex discloses it (sponsor column, else carve-out guarantor, labelled). Each row carries the core property id where the building chain resolved it, for get_property_record. Filter by state, property type, maturity window, distress or sponsor text, or ask for ONE building with property (its name or street address, e.g. 'Park West Village', '1384 Broadway') or property_dfx_id (the id resolve_address or get_property_record gave). The answer to 'Texas multifamily loans maturing in 18 months that are in special servicing, and who sponsors them'. Conduit CMBS only: bank balance sheet, agency and debt fund loans are not on this tape. ACCESS: without a paid DFX plan on the vertical, a list returns its first 5 rows in full and a count of the rest by type (locked.count, locked.by_type), never the rows; a record names its subject and the first 3 related names per section; contact values (email, phone, profile URLs) and decision-maker names are never returned, only their types and counts. Every answer says what it withheld in entitlement and locked. Full access: DFX Intelligence, 7 days free at https://dfxintel.com/data-factory/plans.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_cmbs_loans"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNoTwo-letter state of the property.
cursorNonext_cursor from a previous page of this tool, unchanged.
sponsorNoSponsor or guarantor name contains, as the annex prints it.
distressNospecial_servicing: transferred and not returned; not_current: any payment status other than current; any: either.
dscr_maxNoOnly loans whose latest DSCR is strictly below this (the current filing, else the last DSCR reported within 12 months; each row prints the period it was reported for). 'DSCR under 1.2' is dscr_max 1.2.
propertyNoOne building by its name or street address, as a buyer writes it: 'Renaissance Seattle Hotel', '225 & 233 Park Avenue South', 'One West 34th Street'. Matched on the tape's property name and address after normalising both (case, punctuation, & as and, Street as St); a single house number also finds a range address. Use this, not sponsor, for a building name.
loan_keysNoSpecific loan keys (deal CIK:asset number) from a previous answer.
maturity_toNoISO date.
maturity_fromNoISO date.
property_typeNo
transferred_toNoISO date: special servicing transfer on or before.
property_dfx_idNoA core property id (from resolve_address or get_property_record): the loans on that building, including its notes in other trusts.
transferred_fromNoISO date: special servicing transfer on or after.
maturity_within_daysNoLoans maturing from today to today plus this many days.
transferred_within_daysNoLoans the master servicer transferred to special servicing in the last this many days, by the servicer's own transfer date, newest first. 'Special servicing transfers in the last 90 days' is transferred_within_days 90.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / transferred_from
      Added value: +{
      +  "description": "ISO date: special servicing transfer on or after.",
      +  "type": "string"
      +}
    • addedInput schema / properties / transferred_to
      Added value: +{
      +  "description": "ISO date: special servicing transfer on or before.",
      +  "type": "string"
      +}
    • addedInput schema / properties / transferred_within_days
      Added value: +{
      +  "description": "Loans the master servicer transferred to special servicing in the last this many days, by the servicer's own transfer date, newest first. 'Special servicing transfers in the last 90 days' is transferred_within_days 90.",
      +  "maximum": 3650,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / property
      Added value: +{
      +  "description": "One building by its name or street address, as a buyer writes it: 'Renaissance Seattle Hotel', '225 & 233 Park Avenue South', 'One West 34th Street'. Matched on the tape's property name and address after normalising both (case, punctuation, & as and, Street as St); a single house number also finds a range address. Use this, not sponsor, for a building name.",
      +  "type": "string"
      +}
    • addedInput schema / properties / property_dfx_id
      Added value: +{
      +  "description": "A core property id (from resolve_address or get_property_record): the loans on that building, including its notes in other trusts.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / dscr_max
      Added value: +{
      +  "description": "Only loans whose latest DSCR is strictly below this (the current filing, else the last DSCR reported within 12 months; each row prints the period it was reported for). 'DSCR under 1.2' is dscr_max 1.2.",
      +  "maximum": 10,
      +  "minimum": 0,
      +  "type": "number"
      +}
  4. Added

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description's real added value is the entitlement behavior — a free tier returns only the first 5 rows plus locked.count and locked.by_type, never the rows, and contact values and decision-maker names are withheld — plus the data-recency rule. That is substantive, but it never states pagination limits or how cursor interacts with the free-tier truncation, leaving a gap for a 16-parameter search.

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?

Purpose and scope are front-loaded, and the long middle enumeration is dense but information-bearing since there is no output schema. The trailing 'Full access: DFX Intelligence, 7 days free at https://...' is promotional rather than operational, and the ACCESS block is verbose relative to the rest.

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 no output schema, the description carries the return-shape burden and mostly meets it: it names the row fields, the core property id, the `entitlement` and `locked` keys, and the data vintage. What is missing is pagination/limit behavior and how many rows a paid response can return, which matters for a parameter with a hard maximum of 50.

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 88%, so most parameters are already documented and the baseline is 3. The description still adds meaning the schema does not: that originator is the filed code ('WFB') with the parent lender's name beside it as lender_name, and that sponsor is the prospectus annex column falling back to the carve-out guarantor (labelled). Its property matching hints and dscr_max/distress examples largely restate the schema text, which caps it below 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?

The first sentence names the exact resource (loans on the ACTIVE CMBS tape, from SEC ABS-EE, latest monthly reading) and enumerates the servicer fields returned. It also draws a hard scope boundary — 'Conduit CMBS only: bank balance sheet, agency and debt fund loans are not on this tape' — which separates it from siblings like search_re_fund_loans and search_cmbs_resolutions without the agent opening any schema.

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

Usage Guidelines5/5

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

Explicit routing rules are given: 'Use this, not sponsor, for a building name', property_dfx_id comes from resolve_address or get_property_record, and each row carries the core property id to hand off to get_property_record. It also supplies a concrete worked query ('Texas multifamily loans maturing in 18 months that are in special servicing, and who sponsors them') that maps a natural-language intent onto the filters.

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.