Skip to main content
Glama

Custom Solutions

Net operating income (NOI)

compute_noi
Read-onlyIdempotent

Net operating income (NOI) of a rental property per year: scheduled rent less vacancy, management, maintenance, capital reserve and fixed costs, before any mortgage payment. NOI is easy to overstate: management is charged on rent actually collected, maintenance and reserves on scheduled rent, and the debt payment is left out entirely, so a figure that subtracts the mortgage is cash flow instead. Send the monthly rent for the whole property; vacancy, management, maintenance and capex as percents (8 means 8%); and the yearly fixed costs (tax, insurance, owner-paid utilities, HOA). Any omitted expense counts as 0 and is listed in the answer's inputs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "monthly_rent": "<monthly_rent>"
    },
    "name": "compute_noi"
  }
}

Input Schema

NameRequiredDescriptionDefault
capex_pctNoCapital reserve as a percent of scheduled rent, e.g. 5
vacancy_pctNoVacancy and credit loss as a percent of rent, e.g. 8 for 8%
monthly_rentYesScheduled rent for the whole property per month, in dollars, e.g. 2400
management_pctNoProperty management as a percent of collected rent, e.g. 8
maintenance_pctNoRepairs and maintenance as a percent of scheduled rent, e.g. 8
annual_fixed_costsNoProperty tax, insurance, owner-paid utilities, HOA and other fixed costs per year, e.g. 5400
other_income_monthlyNoLaundry, parking or pet income per month, e.g. 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, closed-world calculation, so the safety profile needs no repeating. Beyond that, the description discloses genuinely non-obvious computation behavior: management applies to collected rent while maintenance and reserves apply to scheduled rent, and debt service is excluded entirely. It also states the defaulting rule that omitted expenses count as zero and are echoed in the answer's inputs, which is exactly the kind of behavior an agent cannot infer from structured fields.

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 formula and the overstatement warning are front-loaded, and the input instructions follow in a single dense sentence with no filler. The prose is long-sentence-heavy and could be tightened, but every clause carries substantive content.

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 seven-parameter calculation tool with no output schema, the definition covers inputs, percentage semantics, defaults for omitted values, and the main conceptual pitfall. The only gap is what the result object contains beyond the echoed inputs, which is minor for an arithmetic helper whose output is implied by its name.

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 schema already documents each field and the baseline would be 3. The description still adds real meaning: it clarifies the percentage convention (8 means 8%), insists the rent figure covers the whole property monthly, and explains which base each percentage is applied to — a distinction absent from the schema descriptions, which all say 'percent of rent'.

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 first sentence names a specific computed quantity (annual NOI of a rental property) and spells out its formula, so an agent knows exactly what it returns. It also pre-empts confusion with the cash-flow sibling by stating that subtracting the mortgage makes it cash flow instead, which cleanly separates it from compute_cash_on_cash.

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?

The description tells the caller what to send (whole-property monthly rent, percentages on a 0-100 scale, annual fixed costs) and warns against the common misuse of netting out debt service, which routes the agent toward the cash-flow tool. It stops short of naming the alternative tool or stating explicit exclusions, so it is clear context rather than a full when/when-not rule set.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources