Skip to main content
Glama

Stratalize Intelligence

Get Cre Debt Benchmark

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

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so the description's main added value is provenance (MBA CREF, Trepp) and the per-call price of $0.02 USDC, which an agent cannot get from structured fields. It does not disclose data vintage, refresh cadence, or whether a benchmark row is returned when the lender/property combination has no coverage.

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

Conciseness5/5

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

Three compact sentences, metric content front-loaded, then source attribution, then audience, then price. No filler, no restatement of the title, and the cost signal is placed last where it does not obstruct the purpose statement.

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 simple two-parameter read tool with no output schema, the description supplies what an agent needs: what metrics come back, how they are sliced, where the data originates, and what it costs. The remaining gap is behavioral edge cases (empty results for unsupported lender/property combinations, data recency) rather than core invocation guidance.

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 description coverage is 0%, but both parameters carry fully enumerated value sets, so the meaning of each option is largely self-documenting. The description reinforces this by naming the axes ('by property type and lender type') and echoing the lender categories (bank, agency, CMBS, life company), though it omits debt_fund and bridge and does not say whether lender_type is optional and what the default aggregation is.

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 a specific resource (CRE debt benchmarks) and enumerates the exact metrics returned: DSCR minimums, LTV maximums, and spread ranges, segmented by property type and lender type. It also cites the underlying sources (MBA CREF databook, Trepp), which pins down scope. It does not explicitly contrast itself with the adjacent credit siblings such as get_real_estate_debt_stress_benchmark, which keeps it from a 5.

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?

Provides audience framing ('For CRE CFOs and capital markets teams structuring financings'), which implicitly signals when the tool fits. There is no explicit when-to-use versus alternatives, no exclusion of the stress-benchmark sibling, and no stated prerequisite that one of the two parameters is required.

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