Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_cap_rate

Calculate capitalization rate, net operating income, and gross rent multiplier from property price, annual rent, and operating costs to obtain precise real estate valuation metrics.

Instructions

Cap Rate (Capitalization Rate) Calculator. Calculate commercial and residential real estate Capitalization Rates (Cap Rate) and valuation multiples from Net Operating Income. Discipline: FINANCE. Governing mathematical model / formula: Cap Rate = (Annual Net Operating Income / Current Market Value) × 100%.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of cap_rate_pct (Capitalization Rate (Cap Rate)), net_operating_income (Annual Net Operating Income (NOI)), gross_rent_multiplier (Gross Rent Multiplier (GRM)) using property_price (Property Purchase Price / Value), gross_annual_rent (Gross Annual Rental Revenue), annual_operating_costs (Annual Operating Expenses). 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 'Cap Rate (Capitalization Rate) 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): "cap-rate"

    • category (string): "finance"

    • name (string): "Cap Rate (Capitalization Rate) Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.cap_rate_pct (Capitalization Rate (Cap Rate)): Formatted display string (e.g. '8.00%')

      • metrics.net_operating_income (Annual Net Operating Income (NOI)): Formatted display string (e.g. '$68,000.00')

      • metrics.gross_rent_multiplier (Gross Rent Multiplier (GRM)): Formatted display string (e.g. '8.85x')

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

Input Schema

NameRequiredDescriptionDefault
property_priceNoProperty Purchase Price / Value. Purchase price or current market value. Default: 850000. Min: 50000. Max: 20000000.
gross_annual_rentNoGross Annual Rental Revenue. Total scheduled annual rent. Default: 96000. Min: 5000. Max: 2000000.
annual_operating_costsNoAnnual Operating Expenses. Property taxes, insurance, repairs, vacancy, management. Default: 28000. Min: 0. Max: 1000000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.1/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 read-only, idempotent, stateless behavior, zero side effects, deterministic floating-point computation, and describes out-of-bounds handling as returning a safe diagnostic error status rather than throwing. It stops short of documenting precision/rounding rules or the exact error payload shape, so not quite maximal.

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?

Front-loaded with purpose and formula, then cleanly sectioned into usage, behavior and returns, so an agent can scan it quickly. It is longer than necessary for a three-parameter calculator, with boilerplate headers and low-value echo fields (calculator, category, name) padding the RETURNS block.

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?

No output schema exists, and the description compensates by documenting every returned field, including that metrics are formatted display strings and that a status/error path exists. For a simple deterministic three-input calculator, that covers everything an agent needs to invoke and interpret the result.

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%, with defaults, min/max bounds and meanings already stated per parameter, so the schema does the heavy lifting. The description maps each parameter name to its domain term (property_price to purchase price/value, annual_operating_costs to taxes/insurance/repairs) but adds no syntax, unit, or defaulting detail beyond the schema; baseline 3 applies.

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?

Names a specific verb and resource ('Cap Rate (Capitalization Rate) Calculator') and enumerates the exact outputs (cap_rate_pct, NOI, GRM) and inputs, plus the governing formula. It also explicitly contrasts itself with the generic dispatcher omni_universal_query, so an agent can tell it apart from non-specialist siblings without opening the schema.

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?

Provides explicit WHEN TO USE, WHEN NOT TO USE, and SIBLING ROUTING sections naming omni_universal_query as the generic alternative. The exclusion ('do not use for qualitative evaluations / inputs must be numeric') is somewhat vacuous and gives no boundary against close numeric siblings, so guidance is strong but not fully discriminating.

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