Skip to main content
Glama

Relendi — Commercial Real Estate Loan Tools

Run a CRE Loan Scenario

run_scenario
Read-only

Run what-if loan sizing across a range of assumptions: a rate ladder, an NOI sensitivity table, or the feasibility of a target loan amount against each constraint. Deterministic — same math as size_loan, swept.

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": {
      "netOperatingIncome": "<netOperatingIncome>",
      "estimatedValue": "<estimatedValue>",
      "mode": "<mode>"
    },
    "name": "run_scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
ratesNo
totalCostNo
thresholdsNo
noiDeltaPctsNo
estimatedValueYes
desiredLoanAmountNo
netOperatingIncomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description usefully adds that the computation is deterministic and swept. It says nothing about what the caller gets back (no output schema exists) or what happens when mode-specific inputs are omitted, which matters for a three-mode tool.

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?

Two tight sentences with the mode enumeration front-loaded and no repeated schema text. Every clause adds information an agent cannot get from the structured fields.

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?

For an 8-parameter, nested-object, no-output-schema tool, the description establishes purpose and modes but omits per-mode input requirements (which fields are needed for feasibility vs. sensitivity), defaults for rates/thresholds, and any sense of the returned structure or result size.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 parameters including a nested thresholds object, so the description carries the full burden. It gestures at the concepts (a rate ladder, an NOI sensitivity table, a target loan amount) but never names or maps them to rates, noiDeltaPcts, desiredLoanAmount or the threshold fields, and gives no defaults or format guidance.

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 ('Run what-if loan sizing') and enumerates the three concrete sweep modes (rate_ladder, noi_sensitivity, loan_feasibility). The closing clause 'same math as size_loan, swept' cleanly separates it from the single-point sibling.

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?

The comparison to size_loan implies when to prefer this tool (you want a sweep rather than a single sizing), which is useful context. But it never states when NOT to use it, and given siblings like stress_test and size_loan that plausibly overlap, no explicit routing or exclusions are offered.

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