Skip to main content
Glama

get_cre_debt_benchmark

Read-only

Commercial real estate debt benchmarks — DSCR minimums, LTV maximums, and spread ranges by property type and lender type (bank, agency, CMBS, life company). Source: MBA CREF databook and Trepp public data. For CRE CFOs and capital markets teams structuring financings. $0.02 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "property_type": "<property_type>"
    },
    "name": "get_cre_debt_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
lender_typeNo
property_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds genuinely new behavior: the upstream data sources (MBA CREF databook, Trepp public data) and the per-call price of $0.02 USDC, which matters for an agent deciding whether to invoke. It stops short of describing data vintage/recency or the shape of the response, which are the remaining behavioral unknowns.

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?

Two tight sentences that front-load the metrics, followed by source and audience/price metadata. The audience sentence ('For CRE CFOs...') is the weakest line and could be trimmed, but nothing is seriously bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 must carry the return-value burden; it partially does by listing which metrics come back and at what granularity, plus the source. It omits data recency/period, units, and output format, which for a benchmark tool are material to correct interpretation.

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 coverage is 0%, but both parameters are closed enums whose values are largely self-describing, and the description does map them to meaning ('by property type and lender type'). It does not explain what happens when the optional lender_type is omitted (all lender types? a default?), leaving the main semantic 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?

Names the specific resource (CRE debt benchmarks) and enumerates the metrics returned (DSCR minimums, LTV maximums, spread ranges) plus the segmentation axes (property type, lender type). It implicitly distinguishes itself from siblings like get_corporate_debt_benchmark by scoping to commercial real estate, but it never names an alternative explicitly.

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

Usage Guidelines2/5

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

The only usage signal is audience framing ('For CRE CFOs and capital markets teams structuring financings'), which implies context but gives no when-to-use/when-not conditions. There is no guidance on choosing this over get_corporate_debt_benchmark or get_real_estate_debt_stress_benchmark, which is the most likely point of confusion.

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