Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_dscr_loan

Calculates Debt Service Coverage Ratio (DSCR) from monthly rent, operating expenses, and mortgage P&I to qualify for real estate investor loans without personal income or tax returns.

Instructions

DSCR (Debt Service Coverage Ratio) Calculator. Calculate Debt Service Coverage Ratio (DSCR) and qualify for real estate investor loans without personal income or tax returns. Discipline: FINANCE. Governing mathematical model / formula: DSCR = Net Operating Income (NOI) / Annual Debt Service.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of dscr_ratio (Debt Service Coverage Ratio (DSCR)), net_operating_income (Monthly Net Operating Income (NOI)), dscr_status (Underwriting Qualification) using monthly_rent (Gross Monthly Rental Income), operating_expenses (Monthly Expenses (Taxes, Ins, HOA)), monthly_pi (Monthly Principal & Interest). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'DSCR (Debt Service Coverage Ratio) Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "dscr-loan"

    • category (string): "finance"

    • name (string): "DSCR (Debt Service Coverage Ratio) Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.dscr_ratio (Debt Service Coverage Ratio (DSCR)): Formatted display string (e.g. '1.36')

      • metrics.net_operating_income (Monthly Net Operating Income (NOI)): Formatted display string (e.g. '$2,850.00')

      • metrics.dscr_status (Underwriting Qualification): Formatted display string (e.g. 'Prime Qualified (DSCR >= 1.25)')

    • execution_time_ms (number): Latency in milliseconds.

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": "omni_dscr_loan"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthly_piNoMonthly Principal & Interest. Mortgage P&I payment. Default: 2100. Min: 200. Max: 25000.
monthly_rentNoGross Monthly Rental Income. Market rent supported by appraisal (Form 1007). Default: 3500. Min: 500. Max: 50000.
operating_expensesNoMonthly Expenses (Taxes, Ins, HOA). Property taxes, insurance, and HOA dues. Default: 650. Min: 0. Max: 10000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are supplied, so the description must carry the full behavioral burden, and it does: read-only, idempotent, stateless, zero side effects, machine floating-point precision, and input validation that returns a safe diagnostic error status instead of throwing on out-of-bounds inputs. It additionally documents the exact return payload (status, formula, echoed inputs, metrics, execution_time_ms), which is essential since no output schema exists.

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?

Well sectioned and front-loaded with purpose, formula, and usage, with labeled blocks that make scanning easy. It loses a point for bulk: the opening lender-qualification sentence is promotional rather than operational, and the RETURNS block repeats labels already present in the metrics descriptions.

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?

Given three numeric parameters, no annotations, and no output schema, the description covers everything an agent needs: what is computed, the formula, input validity constraints, error behavior, and the full shape of the response including formatted display strings. Nothing material is left to inference for a self-contained deterministic calculator.

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 100%, so the schema already carries defaults, min/max bounds, and per-field definitions; that sets a baseline of 3. The description adds meaning beyond that by tying the three inputs to the formula's structure (NOI derived from rent minus operating expenses, then divided by annualized debt service from monthly_pi), which clarifies how the parameters relate rather than just what they are.

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 a specific verb and resource ('Calculate Debt Service Coverage Ratio (DSCR)') and states the governing formula, so the agent knows exactly what is computed. It also distinguishes the tool from generic dispatchers by name, which lets an agent separate it from the long list of sibling calculators.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE (deterministic computation of dscr_ratio, net_operating_income, dscr_status from rent/expenses/P&I), explicit WHEN NOT TO USE (no qualitative reasoning; inputs must be numeric), and named alternatives for related jobs: omni_batch_calculate for chained calculations and omni_describe_solver for schema inspection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools