Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_debt_service_coverage

Calculates DSCR and interest coverage from NOI/EBITDA, principal, and interest to assess commercial loan underwriting and debt service capacity.

Instructions

Corporate DSCR & Interest Coverage Calculator. Calculate Debt Service Coverage Ratio (DSCR) and Times Interest Earned (TIE) from Net Operating Income (NOI) / EBITDA and debt service obligations. Discipline: FINANCE. Governing mathematical model / formula: DSCR = Net Operating Income (NOI) / Total Debt Service (Principal + Interest).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of dscr_score (Debt Service Coverage Ratio (DSCR)), interest_coverage_tie (Interest Coverage (TIE)), total_debt_service (Total Annual Debt Service), underwriting_status (Commercial Bank Underwriting) using ebitda_noi (Net Operating Income (NOI) / EBITDA), annual_principal (Annual Principal Repayments), annual_interest (Annual Interest Expense). 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.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Corporate DSCR & Interest Coverage Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

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): "debt-service-coverage"

    • category (string): "finance"

    • name (string): "Corporate DSCR & Interest Coverage Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.dscr_score (Debt Service Coverage Ratio (DSCR)): Formatted display string (e.g. '1.60× Coverage')

      • metrics.interest_coverage_tie (Interest Coverage (TIE)): Formatted display string (e.g. '3.69× Interest')

      • metrics.total_debt_service (Total Annual Debt Service): Formatted display string (e.g. '$150,000.00 / yr')

      • metrics.underwriting_status (Commercial Bank Underwriting): Formatted display string (e.g. 'Approved (Exceeds 1.25x minimum covenant)')

    • 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_debt_service_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
ebitda_noiNoNet Operating Income (NOI) / EBITDA. Annual cash flow available for debt service. Default: 240000. Min: 10000. Max: 50000000.
annual_interestNoAnnual Interest Expense. Interest payments on all outstanding loans. Default: 65000. Min: 1000. Max: 20000000.
annual_principalNoAnnual Principal Repayments. Mandatory loan principal amortization. Default: 85000. Min: 0. Max: 20000000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so well: it declares the tool read-only, idempotent, stateless, with zero side effects, and describes the validation behavior (out-of-bounds inputs return a safe diagnostic error rather than throwing). The only thing keeping this from a 5 is that the safety claims are asserted rather than tied to any annotation or error-code detail beyond the generic 'error' status.

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 is front-loaded with the purpose and formula, then cleanly sectioned into usage, behavior, and returns, which makes it easy to scan. It is somewhat long and repeats itself, stating the DSCR formula twice and re-expanding each parameter name in the usage section that the schema already documents, but that repetition is mild rather than wasteful.

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 no annotations and no output schema, the description compensates on both fronts: it supplies the full behavioral profile (read-only, stateless, validation errors) and enumerates every returned field, including the formatted display strings in the metrics object. Combined with 100% schema coverage on all three parameters, nothing an agent needs in order to call or interpret this tool is missing.

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 the baseline is 3, but the description goes further by mapping each parameter to its role in the formula ('ebitda_noi' as NOI/EBITDA, 'annual_principal' and 'annual_interest' summing to Total Debt Service). That relational meaning is not present in the schema and helps an agent understand how the three inputs combine, though it still doesn't discuss units or the min/max bounds the schema already covers.

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 pair immediately ('Calculate Debt Service Coverage Ratio (DSCR) and Times Interest Earned (TIE)') and states the governing formula, so an agent knows exactly what it computes and what inputs feed it. It also explicitly separates itself from the generic dispatcher, so there is no ambiguity about which tool handles corporate DSCR/TIE.

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?

Three explicit sections cover WHEN TO USE, WHEN NOT TO USE, and SIBLING ROUTING. The 'when not to use' clause names the disqualifying conditions (qualitative reasoning, non-numeric inputs), and the routing note names the alternative dispatcher tool by name, which is exactly the when/when-not/alternative structure a strong definition needs.

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