Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_rental_cash_flow

Calculate rental property net monthly cash flow, annual cash flow, and cash-on-cash return from rent, mortgage, taxes, insurance, vacancy/CapEx, and cash invested.

Instructions

Rental Property Cash Flow & ROI Calculator. Calculate monthly net cash flow, Cash-on-Cash Return (CoC), and expense ratios for residential investment real estate. Discipline: FINANCE. Governing mathematical model / formula: Cash-on-Cash Return = (Annual Net Cash Flow / Total Cash Invested) × 100%.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of net_monthly_cashflow (Net Monthly Cash Flow), annual_cashflow (Annual Net Cash Flow), cash_on_cash_return (Cash-on-Cash Return (CoC)) using monthly_rent (Monthly Rental Income), monthly_mortgage (Monthly Mortgage (P&I)), monthly_taxes_ins (Monthly Taxes & Insurance), capex_vacancy_pct (CapEx, Maintenance & Vacancy (%) in %), total_cash_invested (Total Initial Cash Invested). 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 'Rental Property Cash Flow & ROI 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): "rental-cash-flow"

    • category (string): "finance"

    • name (string): "Rental Property Cash Flow & ROI Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.net_monthly_cashflow (Net Monthly Cash Flow): Formatted display string (e.g. '$510.00')

      • metrics.annual_cashflow (Annual Net Cash Flow): Formatted display string (e.g. '$6,120.00')

      • metrics.cash_on_cash_return (Cash-on-Cash Return (CoC)): Formatted display string (e.g. '8.16%')

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

Input Schema

NameRequiredDescriptionDefault
monthly_rentNoMonthly Rental Income. Gross rent collected. Default: 2800. Min: 500. Max: 25000.
monthly_mortgageNoMonthly Mortgage (P&I). Debt service payment. Default: 1450. Min: 0. Max: 15000.
capex_vacancy_pctNoCapEx, Maintenance & Vacancy (%) (%). Reserves for maintenance and downtime. Default: 15. Min: 5. Max: 30.
monthly_taxes_insNoMonthly Taxes & Insurance. Property tax and hazard insurance. Default: 420. Min: 0. Max: 5000.
total_cash_investedNoTotal Initial Cash Invested. Down payment + closing costs + rehab. Default: 75000. Min: 5000. Max: 500000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.3/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 behavioral disclosure. It states deterministic machine floating-point computation, read-only/idempotent/stateless behavior, zero side effects, and input validation that returns a diagnostic error without runtime exceptions.

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 structured with a front-loaded purpose and clearly separated usage, boundaries, behavior, and returns sections. It is lengthy for a five-parameter calculator and repeats input labels and output metrics, but the text is generally purposeful.

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?

With no output schema and no annotations, the description carries the full burden and does describe status, metrics, echoed inputs, formula, and execution time. The only notable gap is that it promises expense ratios in the purpose but does not list an expense-ratio metric in RETURNS.

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 description coverage is 100%, so the schema already documents all five parameters with defaults and min/max bounds. The description repeats parameter labels but adds no calculation details beyond naming the inputs, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and verb: Rental Property Cash Flow & ROI Calculator computing net monthly cash flow, CoC, and expense ratios for residential real estate. It distinguishes from generic dispatchers and batch tools, but the opening claim about expense ratios is not reflected in the returned metrics, and it does not address the similarly named cash_on_cash_return sibling.

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?

Has explicit WHEN TO USE and WHEN NOT TO USE sections, names omni_universal_query and omni_batch_calculate as alternatives, and warns that all inputs must be valid numerical values. The closest sibling routing is not explicit, but the section otherwise provides clear when/when-not/alternatives guidance.

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