Skip to main content
Glama

Commercial real estate debt by sponsor, lender or servicer in a maturity window

get_re_debt_exposure
Read-onlyIdempotent

CMBS debt grouped by who carries it (latest reading per loan on the SEC ABS-EE tape): group=sponsor (the prospectus annex's sponsor or carve-out guarantor, by normalised name family), lender (the originator, folded to its parent where an SEC prospectus links them), servicer or special_servicer. Filters: within_months (default 24), property_type, state, distress (special_servicing, not_current, any), min_balance on the group's total, name (one family). Sorted by balance, with loans, properties, special servicing and the largest notes. A co-sponsored note counts in full to each named sponsor and is flagged. Conduit CMBS only. 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": "get_re_debt_exposure"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOne sponsor or lender name family.
groupNosponsor
limitNo
stateNoTwo-letter US state code.
distressNo
min_balanceNoUSD floor on the group's total in the window.
property_typeNo
within_monthsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive/closed-world), the description discloses the entitlement model: without a paid plan a list returns only its first 5 rows plus locked.count/locked.by_type and never the rows, contact values and decision-maker names are never returned, and every response reports withholdings in `entitlement` and `locked`. It also explains sorting, the co-sponsored-note counting rule, and that a co-sponsor is flagged -- genuinely load-bearing behavior an agent cannot get from the schema or annotations.

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 and grouping options are front-loaded, and the access/entitlement sentences each carry real information. It is dense and long, and the closing plan pitch with a signup URL is promotional rather than functional, but the description is mostly structured and earns its length.

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?

For a complex 8-parameter tool with no output schema and no required parameters, the description covers what is returned (groups sorted by balance, with loans, properties, special servicing, largest notes), how filters scope the result, and how entitlement truncates output. Nothing essential for correct invocation is missing.

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?

With only 38% schema description coverage, the description does most of the work: it defines group values, distress values, min_balance as a floor on the group's total, name as a single name family, and within_months default. Only `limit` is left unexplained, so the description substantially compensates for the coverage gap.

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

Purpose4/5

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

The description gives a precise verb+resource+scope: 'CMBS debt grouped by who carries it', with the four valid grouping dimensions spelled out (sponsor/lender/servicer/special_servicer) and a hard boundary ('Conduit CMBS only'). An agent can tell this is an aggregate-exposure view rather than a loan list, though no sibling (e.g. search_cmbs_loans, search_bank_cre_exposure) is named to anchor the distinction.

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

Usage Guidelines3/5

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

Usage is implied through the filter list (within_months, property_type, state, distress, min_balance, name) and the default 24-month maturity window, so an agent can infer when the tool fits. There is no explicit when-to-use/when-not guidance and no routing to alternatives for loan-level or bank-CRE queries, leaving the agent to infer.

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.