Skip to main content
Glama

Custom Solutions

Debt service coverage ratio (DSCR)

compute_dscr
Read-onlyIdempotent

Debt service coverage ratio of a rental, two ways: NOI divided by yearly principal and interest, and the figure DSCR-loan lenders use on 1-4 unit rentals, scheduled rent divided by PITIA (payment plus tax, insurance and HOA). The two definitions give different numbers for the same property, which is why quotes of a DSCR often disagree; both are labelled in the answer. With target_dscr, rate_pct and amort_years the answer also sizes the largest loan the NOI supports. Send noi and annual_debt_service, plus gross_rent_annual, annual_tax, annual_insurance and annual_hoa for the lender figure. Zero debt service is refused: with no debt, DSCR does not exist.

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": {
      "noi": "<noi>",
      "annual_debt_service": "<annual_debt_service>"
    },
    "name": "compute_dscr"
  }
}

Input Schema

NameRequiredDescriptionDefault
noiYesNet operating income per year, e.g. 28000
rate_pctNoLoan interest rate in percent, e.g. 7.25, for the largest loan
annual_hoaNoHOA dues per year, e.g. 0, for the lender figure
annual_taxNoProperty tax per year, e.g. 3600, for the lender figure
amort_yearsNoAmortization in years, e.g. 30, for the largest loan
target_dscrNoLender minimum DSCR, e.g. 1.25, to size the largest loan
annual_insuranceNoInsurance per year, e.g. 1800, for the lender figure
gross_rent_annualNoScheduled rent per year, e.g. 38400, for the lender rent-to-PITIA figure
annual_debt_serviceYesPrincipal and interest paid per year, e.g. 22000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine behavior beyond them: both figures are returned and labelled, the loan-sizing branch activates only with target_dscr/rate_pct/amort_years, and a zero-debt-service call is rejected with a stated reason.

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 leads with the resource and definitional split, then the required inputs, then the optional branches, ending with the refusal condition. Sentences are dense with formulas and examples, so it is heavier than ideal, but no sentence is filler.

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?

There is no output schema, and the description compensates by saying both ratios come back labelled and that loan sizing is added when the relevant inputs are present. For a 9-parameter read-only calculator, an agent has everything needed to call it correctly and interpret the result.

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%, so a baseline of 3 applies, but the description adds the conditional grouping the schema states only per-field: which parameters are needed for the lender figure (gross rent plus tax, insurance, HOA) versus which size the largest loan. That dependency structure is meaningfully beyond a flat field list.

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?

The description names the specific metric (DSCR) and precisely defines the two computations it returns: NOI / annual principal & interest, and scheduled rent / PITIA. It also explains why two definitions exist, which distinguishes this from the narrower compute_noi and compute_mortgage_payment siblings.

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

Usage Guidelines4/5

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

It states clearly which inputs are required (noi and annual_debt_service) and which extra inputs unlock the lender figure and the loan-sizing output. It also declares an exclusion (zero debt service is refused). It does not explicitly route the agent to or away from a named sibling, which keeps it below a 5.

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