Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_gross_rent_multiplier

Calculate property Gross Rent Multiplier and estimate fair market value from annual gross rent. Compares purchase price to a market GRM benchmark to flag overpriced or underpriced deals.

Instructions

Gross Rent Multiplier (GRM) & Valuation Calculator. Calculate Gross Rent Multiplier (GRM) and estimate fair market multifamily property values from annual gross scheduled rents. Discipline: FINANCE. Governing mathematical model / formula: GRM = Property Purchase Price / Gross Annual Scheduled Rent | Property Value = Gross Rent × GRM.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of actual_grm_result (Property Gross Rent Multiplier), market_fair_value (Indicated Value at Market GRM (8.5)), monthly_gross_rent (Monthly Gross Scheduled Rent), valuation_verdict (Pricing Relative to Market) using property_price_grm (Property Purchase Price / Valuation), gross_annual_rent (Gross Annual Scheduled Rent), market_target_grm (Comparable Market GRM Benchmark). 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 'Gross Rent Multiplier (GRM) & Valuation 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): "gross-rent-multiplier"

    • category (string): "finance"

    • name (string): "Gross Rent Multiplier (GRM) & Valuation Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

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

      • metrics.market_fair_value (Indicated Value at Market GRM (8.5)): Formatted display string (e.g. '$816,000.00')

      • metrics.monthly_gross_rent (Monthly Gross Scheduled Rent): Formatted display string (e.g. '$8,000.00 / mo')

      • metrics.valuation_verdict (Pricing Relative to Market): Formatted display string (e.g. 'Priced Above Market (Overpriced by $34,000)')

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

Input Schema

NameRequiredDescriptionDefault
gross_annual_rentNoGross Annual Scheduled Rent. Total gross rental income before expenses. Default: 96000. Min: 5000. Max: 20000000.
market_target_grmNoComparable Market GRM Benchmark. Average GRM of recent comparable neighborhood sales. Default: 8.5. Min: 3. Max: 25.
property_price_grmNoProperty Purchase Price / Valuation. Asking or market price. Default: 850000. Min: 50000. Max: 100000000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/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 well: it declares read-only, idempotent, stateless behavior with zero side effects, and specifies that out-of-bounds inputs return a safe diagnostic error rather than throwing. What it omits is minor for a pure calculator — no auth or rate-limit notes — but it compensates by stating determinism and floating-point precision.

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?

Is front-loaded with the purpose and formula, and the sectioned layout (USAGE, DISAMBIGUATION, BEHAVIOR, RETURNS) makes it scannable. The verbosely-labelled output list and repeated reading of the same parameters in the WHEN TO USE sentence add some bulk that does not fully earn its place.

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?

No output schema exists, so the RETURNS section listing status, calculator, category, formula, echoed inputs, and each formatted metric is genuinely necessary and complete. Given a simple three-parameter deterministic calculator, nothing an agent needs to call it correctly is missing.

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% with per-parameter descriptions, defaults, and min/max bounds already in the input schema, so the baseline of 3 applies. The description restates the parameters by name and role but adds no new syntax or interaction guidance beyond what the schema documents.

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?

States a specific verb and resource ('Calculate Gross Rent Multiplier (GRM) and estimate fair market multifamily property values') along with the governing formulas, so the agent knows exactly what computation happens. It explicitly names the generic dispatcher omni_universal_query as the thing it is not, which separates it from siblings.

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 an explicit WHEN TO USE section tying invocation to the three numeric inputs and the four outputs, plus a WHEN NOT TO USE section excluding qualitative reasoning and non-numeric inputs. It names concrete alternatives — omni_batch_calculate for chained jobs, omni_describe_solver for schema inspection, omni_universal_query as the generic fallback.

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