Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_commercial_mortgage

Calculate commercial mortgage monthly payments, balloon balances, and principal retired for multifamily, office, and retail properties from loan amount, interest rate, amortization, and balloon term.

Instructions

Commercial Real Estate Mortgage Calculator. Calculate commercial mortgage monthly payments, balloon balances, and debt yields for multifamily, office, and retail properties. Discipline: FINANCE. Governing mathematical model / formula: M = P · [r(1 + r)ⁿ] / [(1 + r)ⁿ - 1] (with Balloon at Year t).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of monthly_payment (Monthly Debt Service), balloon_amount (Balloon Balance at Maturity), total_principal_paid (Principal Retired at Balloon) using loan_amount (Commercial Loan Amount), interest_rate (Interest Rate (%) in %), amort_years (Amortization Schedule (Years) in yrs), balloon_years (Loan Maturity / Balloon Term in yrs). 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 'Commercial Real Estate Mortgage 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): "commercial-mortgage"

    • category (string): "finance"

    • name (string): "Commercial Real Estate Mortgage Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.monthly_payment (Monthly Debt Service): Formatted display string (e.g. '$14,463.14')

      • metrics.balloon_amount (Balloon Balance at Maturity): Formatted display string (e.g. '$1,542,880.00')

      • metrics.total_principal_paid (Principal Retired at Balloon): Formatted display string (e.g. '$457,120.00')

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

Input Schema

NameRequiredDescriptionDefault
amort_yearsNoAmortization Schedule (Years) (yrs). Base payment amortization period (typically 20-30 yrs). Default: 25. Min: 15. Max: 30.
loan_amountNoCommercial Loan Amount. Total CRE debt amount. Default: 2000000. Min: 250000. Max: 50000000.
balloon_yearsNoLoan Maturity / Balloon Term (yrs). Time until full balloon payment is due. Default: 10. Min: 5. Max: 20.
interest_rateNoInterest Rate (%) (%). Fixed commercial interest rate. Default: 7.25. Min: 4. Max: 14.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.3/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: read-only, idempotent, stateless, zero side effects, bounded input validation returning a diagnostic error rather than throwing. The one blemish is that the opening claims debt-yield calculation while the RETURNS block lists no debt-yield metric, leaving a behavior an agent might expect unaccounted for.

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 long but clearly sectioned and front-loaded, with the purpose and formula stated before usage, boundaries, and returns. A few items are redundant with the schema (units and bounds repeated in prose), which costs it a point, but nothing is buried or wasteful enough to impede scanning.

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 four-parameter deterministic calculator with no output schema, the description fully specifies the return object, error semantics, and determinism guarantees. Completeness is docked only for the unfulfilled debt-yield mention and for not explaining how amort_years and balloon_years interact to produce the balloon balance.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents each parameter with units, defaults, and min/max bounds. The description restates the units and the input-to-output mapping but adds no format guidance, edge-case behavior, or interaction semantics (e.g., balloon_years vs amort_years) beyond what the schema provides, so the baseline 3 is correct.

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 commercial mortgage monthly payments, balloon balances, and debt yields') and then enumerates the exact outputs (monthly_payment, balloon_amount, total_principal_paid). The DISAMBIGUATION section explicitly separates it from omni_universal_query, omni_batch_calculate, and omni_describe_solver, so an agent can route without opening schemas.

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?

It provides an explicit WHEN TO USE block tying each input to its output, a WHEN NOT TO USE block excluding qualitative reasoning and non-numeric inputs, and named alternatives for batching and schema inspection. Nothing about when to select or skip this tool is left to inference.

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