Skip to main content
Glama

get_real_estate_debt_stress_benchmark

Read-only

CRE debt stress benchmarks — live delinquency rate from FRED, CMBS delinquency by property type, maturity wall exposure, and stressed cap rate scenarios. For lenders, special servicers, distressed investors, and regulators. Delinquency rate updates quarterly. $0.02 USDC per call.

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_real_estate_debt_stress_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenarioNo
property_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: data provenance (FRED), update cadence (quarterly), and a per-call price of $0.02 USDC. It still omits what the response looks like and whether the two optional parameters have defaults.

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 definition is front-loaded with the resource and its contents, then adds provenance, cadence, audience, and pricing in tight sequence. Every sentence carries information; only the audience list is arguably filler.

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?

For a read-only, no-output-schema tool with two optional enum parameters, the description covers sources, cadence, cost, and subject matter well. The main remaining gap is default behavior when called with no arguments, which matters because both parameters are optional.

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 0%, so the description has to carry the parameter burden. It partially does: 'CMBS delinquency by property type' maps to property_type, and 'stressed cap rate scenarios' hints at the scenario switch. However, the actual enum levels (base/stress/severe_stress and the property-type values) and the effect of omitting both parameters are never explained.

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 names a specific resource (CRE debt stress benchmarks) and enumerates the concrete contents: FRED delinquency rate, CMBS delinquency by property type, maturity wall exposure, and stressed cap rate scenarios. That is enough to separate it from generic siblings like get_cre_debt_benchmark, though it never says explicitly how it differs from that closest neighbor.

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 only through the audience list ('for lenders, special servicers, distressed investors, and regulators'). There is no explicit when-to-use or when-not guidance and no named alternative (e.g., get_cre_debt_benchmark or get_cap_rate_benchmark), so an agent must infer the boundary.

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