Skip to main content
Glama

cmbs.news: CMBS loan data

CMBS distress index

distress_index
Read-onlyIdempotent

Returns the cmbs.news distress index: delinquency, special-servicing and matured-unpaid rates (balance-weighted, every trust that files a loan-level tape; the headline view adds this month with the older trusts read from their 10-D reports), this month's transfers in and out of special servicing, and rates by property type. Set view for one part, or for more: vintage, state, series (every month since December 2016) or seasoning. Open data under CC BY 4.0. Use it for market-wide rates and trends; use wire for the individual loans that changed this month.

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": "distress_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoWhich part of the index to return. Leave out for the latest rates, this month's flows and rates by property type. vintage also has type by vintage; series is the monthly history; seasoning is how the age of the pool moves the rates

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "Which part of the index to return. Leave out for the latest rates, this month's flows and rates by property type. vintage also has type by vintage; series is the monthly history; seasoning is how the age of the pool moves the rates",
      +  "enum": [
      +    "headline",
      +    "flows",
      +    "type",
      +    "vintage",
      +    "state",
      +    "series",
      +    "seasoning"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed read, so the description is free to spend its words on methodology instead: balance-weighted aggregation, which trusts are included (every trust filing a loan-level tape), and how the headline view incorporates freshly filed 10-D reports. It also discloses licensing (CC BY 4.0) and the historical depth of the series. It stops short of stating refresh cadence or how partial-month reporting affects comparability, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and nothing is pure filler, but the body is a single over-stuffed sentence with deeply nested parentheticals, which makes it slow to parse for an agent skimming for the `view` semantics. Splitting the return contents, the view options, and the sibling alternative into distinct sentences would cost nothing and read far better.

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?

With no output schema, the description carries the burden of saying what comes back, and it does: named rate categories, flow data, property-type breakdowns, plus coverage scope and licensing. For a one-parameter, annotation-covered read tool, an agent has everything it needs to call this 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% and the enum is already documented, so the schema sets a floor of 3. The description earns above that by explaining intent rather than restating: `view` can be set for one part or several, `vintage` also carries type-by-vintage, `series` spans every month since December 2016, and `seasoning` is framed as how pool age moves the rates.

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 ("Returns the cmbs.news distress index") and then enumerates the actual contents: delinquency, special-servicing and matured-unpaid rates, monthly transfers, and rates by property type. It explicitly contrasts itself with the sibling `wire`, so an agent can route between the two without opening a 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?

Gives an explicit use case ("market-wide rates and trends") plus an explicit alternative and the condition that selects it ("use wire for the individual loans that changed this month"). It also states the default behavior when `view` is omitted, removing the main remaining ambiguity.

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.

Resources